[SM-1694] serviceassembly deployment is blocked/delayed by already loaded serviceassemblies

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 3.3
• Component/s: servicemix-assembly
• Patch Info: Patch Available
• Assignee: Unassigned
• Reporter: GShenoy
• Created: 18/Nov/08 00:49
• Updated: 26/Mar/13 13:36
• Resolved: 26/Mar/13 13:36

Description

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.

Issue Links

• depends upon: SM-1607 JBI container should be able to initialize all SAs first and then start them

Sub-Tasks

• BeanEndpoint can receive messages before it has fully started, causing exceptions: Resolved