You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2008/07/23 15:27:00 UTC

[jira] Created: (SMX4KNL-63) Possible deadlock at startup caused by the filedeployer not running in its own thread the first time

Possible deadlock at startup caused by the filedeployer not running in its own thread the first time
----------------------------------------------------------------------------------------------------

                 Key: SMX4KNL-63
                 URL: https://issues.apache.org/activemq/browse/SMX4KNL-63
             Project: ServiceMix Kernel
          Issue Type: Bug
    Affects Versions: 1.0-rc1
            Reporter: Guillaume Nodet
            Assignee: Guillaume Nodet
             Fix For: 1.0.0




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (SMX4KNL-63) Possible deadlock at startup caused by the filedeployer not running in its own thread the first time

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SMX4KNL-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet resolved SMX4KNL-63.
------------------------------------

    Resolution: Fixed

Sending        trunk/filemonitor/src/main/java/org/apache/servicemix/kernel/filemonitor/FileMonitor.java
Transmitting file data .
Committed revision 679087.

> Possible deadlock at startup caused by the filedeployer not running in its own thread the first time
> ----------------------------------------------------------------------------------------------------
>
>                 Key: SMX4KNL-63
>                 URL: https://issues.apache.org/activemq/browse/SMX4KNL-63
>             Project: ServiceMix Kernel
>          Issue Type: Bug
>    Affects Versions: 1.0-rc1
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>             Fix For: 1.0.0
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.