[
https://issues.apache.org/jira/browse/QPID-5177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778593#comment-13778593
]
Rob Godfrey commented on QPID-5177:
-----------------------------------
I believe that the cause here must be a bug in ActiveMQ. As you observe,
sync_publish works fine against Service Bus. I have also tested that it works
against the Qpid Java Broker.
What sync_publish does is to send the message (in AMQP terms it sends the
"transfer" operation) and then waits for the receiver of the message to send
back a "disposition" for the message. It would seem that if it is hanging then
this is because ActiveMQ is not sending back the required disposition
operation. The client should throw an exception after 30s (configurable) to
say that it has timed out.
Have you raised raised a JIRA against ActiveMQ for them to look into this issue?
> producer.send with sync_publish=true set against activemq blocks and doesn't
> return
> -----------------------------------------------------------------------------------
>
> Key: QPID-5177
> URL: https://issues.apache.org/jira/browse/QPID-5177
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.24
> Environment: Qpid 0.22, 0.24, ActiveMQ 5.8.0, Java 7 x64, Ubuntu
> linux 12.04
> Reporter: Troy Collinsworth
>
> While producer.send with system property sync_publish=true against activemq
> block failing to return, the same scenario works fine against Microsoft Azure
> Service Bus.
> This interferes with testing isolated local systems without remote MS ASB
> integration.
> This was not tested against either of the Qpid brokers or the Active MQ 5.9.0
> codebase.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
