You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@servicemix.apache.org by "GShen (JIRA)" <ji...@apache.org> on 2008/11/18 01:54:05 UTC

[jira] Updated: (SM-1694) serviceassembly deployment is blocked/delayed by already loaded serviceassemblies

     [ https://issues.apache.org/activemq/browse/SM-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

GShen updated SM-1694:
----------------------

    Attachment: sm-1694.diff

> serviceassembly deployment is blocked/delayed by already loaded serviceassemblies
> ---------------------------------------------------------------------------------
>
>                 Key: SM-1694
>                 URL: https://issues.apache.org/activemq/browse/SM-1694
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-assembly
>    Affects Versions: 3.3
>            Reporter: GShen
>         Attachments: sm-1694.diff
>
>
> We notice an issue with servicemix 3.3 where serviceassemblies that start processing after start up, block other serviceassemblies from deploying/starting up. The issue occurs when the serviceassembly that is deployed does not immediately return from a serviceunit in its route. Fix  SM-1171 introduced a lock during routing causing service units that take a longer time processing data to block other serviceassemblies from starting up. Adding a patch that should fix SM-1171 while reducing the scope of the lock so it doesnt interfere with assembly startup.

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