[
https://issues.apache.org/activemq/browse/SM-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47525#action_47525
]
GShenoy commented on SM-1694:
-----------------------------
My understanding is that the lock as it existed in patch for SM-1171 was only
to prevent reads before the assembly startup has commenced when autodeployment
holds a write lock. The modified patch provided allows for that here. Hence i
feel it covers SM-1171. I definitely support SM-1607 since that would remove
this extra redundant step of readlocking everytime we route. But until then the
issue of serviceassemblies being blocked will exist.
> 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.
