You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2007/02/26 20:06:03 UTC
[jira] Commented: (AMQ-1123) Deadlocks can occur with even with
sync sends since they share a connection.
[ https://issues.apache.org/activemq/browse/AMQ-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38595 ]
Hiram Chirino commented on AMQ-1123:
------------------------------------
Workaround fix has been implemented in http://svn.apache.org/viewvc?view=rev&revision=511078 in the 4.1 branch.
Basically, if producer uses sync sends, he now can not block another producer on the shared connection. To force all sends to be done sync, a new 'useSyncSend' option has been add to the ActiveMQConnectionFactory.
We should consider implementing a more robust soultion that will work even with async sends in 5.0. This could be done by using producer flow control with acks similar to how we flow control consumers.
> Deadlocks can occur with even with sync sends since they share a connection.
> ----------------------------------------------------------------------------
>
> Key: AMQ-1123
> URL: https://issues.apache.org/activemq/browse/AMQ-1123
> Project: ActiveMQ
> Issue Type: Bug
> Reporter: Hiram Chirino
> Assigned To: Hiram Chirino
>
> If a producer sends to a queue and blocks, any other producer sharing the same connection even if he would be sending to an empty queue would also block. This in effect can cause a deadlock if the right message processing flow is set up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.