[
http://jira.jboss.com/jira/browse/JBMESSAGING-962?page=all ]
Ralf Torsten Menche updated JBMESSAGING-962:
--------------------------------------------
Attachment: TestJBossJMSDeadlock.zip
The zip file contains a small test program (except jboss-messaging-client-1.0.1.SP5.jar;
please copy this jar into TestJBossJMSDeadlock\lib or update the corresponding property in
build.xml).
You also have to change or override the property "jboss.server.host" to point to
a machine where a JBoss with Messaging is running.
Start a publisher with
ant -Dpublisher.cycle.ms=2 run_publisher
and several subscribers with something like
ant -Dsubscriber.cycle.ms=1123 run_subscriber
The property publisher.cycle.ms determines the pause between to published messages,
whereas subscriber.cycle.ms defines the time before the JMS session is restarted (0 for no
restart).
In our environment it takes about a couple of hours until the deadlock occurs.
Fix deadlock in PointToMultipointRouter
---------------------------------------
Key: JBMESSAGING-962
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-962
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.0.1.SP5, 1.2.0.SP1
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.2.0.SP2
Attachments: TestJBossJMSDeadlock.zip
Need to fix deadlock in PointToMultipointRouter - this is a similar deadlock to that in
the other routers and fixed in
http://jira.jboss.org/jira/browse/JBMESSAGING-505 but for
some reason the fix wasn't applied to the PointToMultiPointRouter
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira