[
https://issues.apache.org/activemq/browse/SM-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47513#action_47513
]
Guillaume Nodet commented on SM-1694:
-------------------------------------
Your patch just make the lock useless and will re-enable SM-1171 i think.
We plan to improve the SA startup as part of SM-1607. I think this would need
to acquire the write lock before starting all SAs and releasing it once they
have all been started. This should solve your problem too I think.
> 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: GShenoy
> 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. Attaching modification to SM-1171 patch reducing the scope of the lock
> so it doesn't interfere with other assembly startups.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
