[SM-1868] Deadlock using SedaFlow & Camel Component during SMX start

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.3
• Component/s: servicemix-core

Environment

JDK 1.5, SedaFlow

• Assignee: Freeman Yue Fang
• Reporter: Maciej Prochniak
• Created: 12/Jun/09 11:43
• Updated: 15/Jun/09 08:28
• Resolved: 15/Jun/09 08:28

Description

The scenario is as follows:

• http request is sent to HttpEndpoint
• it's sent to Component A which uses push delivery (e.g. Camel) .
• the camel component processes request - which holds readLock on SedaFlow as push delivery is used.
• deployment of another SA is started - it calls suspend on SedaFlow, acquires SedaFlow object as monitor and waits for writeLock
• Component A sends request to Component B (ODE in our case). The SedaQueue object for Component B is not created yet, so createQueue method in SedaFlow is called, but it's synchronized on the flow object - and deadlock appears

Note: this is different situation than in http://issues.apache.org/activemq/browse/SM-1824

Sub-Tasks

• BUG in JDK6 ReentrantReadWriteLock can cause SMX hang when redeploy SA: Resolved