AutoDeploymentService hangs on deployment of cxf-bc in-out jms consumer when
in-out provider has already placed messages on queue
---------------------------------------------------------------------------------------------------------------------------------
Key: SM-1840
URL: https://issues.apache.org/activemq/browse/SM-1840
Project: ServiceMix
Issue Type: Bug
Components: servicemix-core
Affects Versions: 3.2.4
Environment: JDK 5 Update 16, Windows XP, SMX 3.2.4-SNAPSHOT
Reporter: Ron Gavlin
Priority: Critical
Attached, please find two service assemblies, wsdl-first-cxf-bridge-sa.jar and
wsdl-first-cxf-sa.jar. Perform the following steps to reproduce this blocker
issue:
1. Start SMX
2. Deploy wsdl-first-cxf-bridge-sa.jar
3. Open the cxf-wsdl-first client.html in a browser and send a request message
(note that a jms message is placed on the ActiveMQ person.queue queue)
4. Deploy wsdl-first-cxf-sa.jar (note that the AutoDeploymentService hangs
while attempting to deploy this service assembly)
The following thread dump, generated by the JDK jstack tool, provides insight
into the state of the hung AutoDeploymentService thread:
{quote}
"Timer-3" daemon prio=6 tid=0x2a25c400 nid=0x960 waiting on condition
[0x2b19f000..0x2b19fb14]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x07727260> (a
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:747)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:778)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1114)
at
java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:807)
at
org.apache.servicemix.jbi.nmr.flow.AbstractFlow.suspend(AbstractFlow.java:136)
- locked <0x076fd6d0> (a
org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow)
at
org.apache.servicemix.jbi.nmr.DefaultBroker.suspend(DefaultBroker.java:250)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:250)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:667)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(AutoDeploymentService.java:62)
at
org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:631)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
{quote}
Please let me know if you would like the sources for this project. Also, please
note that this problem also occurs when the smx-cxf-bc in-out jms provider and
consumer endpoints are replaced with either the new or old smx-jmx endpoints.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
