[ http://jira.activemq.org/jira//browse/AMQ-465?page=all ]
Hiram Chirino resolved AMQ-465:
-------------------------------
Resolution: Fixed
The asyncDispatch setting configured on the connection was not being honored by
the connectionConsumers. Fixed so now the default should be to do async
dispatch so the deadlock should not occur with the default configuration
anymore.
> deadlock when using VM transport and Jencks...
> ----------------------------------------------
>
> Key: AMQ-465
> URL: http://jira.activemq.org/jira//browse/AMQ-465
> Project: ActiveMQ
> Type: Bug
> Versions: 4.0 M4
> Reporter: james strachan
> Assignee: Hiram Chirino
> Fix For: 4.1
>
>
> Background here: http://forums.logicblaze.com/posts/list/146.page
> It seems to be VM protocol specific
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.activemq.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
