On Wed, 15 Aug 2018 at 11:13, Gordon Sim <g...@redhat.com> wrote: > > On 15/08/18 10:07, BYRNE Fergus wrote: > > Hi Gordon, > > > > Thanks for your fast response. I have made the changes suggested and I > > still get the same behaviour. > > > > Output from the test > > ----- > > 2018-08-15 09:52:43,305 [localhost:5672]] - INFO SaslMechanismFinder > > - Best match for SASL auth was: SASL-ANONYMOUS > > 2018-08-15 09:52:43,347 [localhost:5672]] - INFO JmsConnection > > - Connection ID:652c4867-137b-4095-a3b3-adb492f5bd89:1 connected to > > remote Broker: amqp://localhost:5672 > > 2018-08-15 09:52:43,396 [main ] - INFO > > RequestResponseReplyToTest - Temporary Response Queue: > > amqp:/_$temp.Cm8IWdyj4NAZKiy > > 2018-08-15 09:52:43,415 [main ] - INFO > > RequestResponseReplyToTest - Temporary Response Queue Consumer Created: > > amqp:/_$temp.Cm8IWdyj4NAZKiy > > 2018-08-15 09:52:43,483 [main ] - INFO > > RequestResponseReplyToTest - Sent request: requests > > 2018-08-15 09:52:43,484 [main ] - INFO > > RequestResponseReplyToTest - > > MessageID:ID:652c4867-137b-4095-a3b3-adb492f5bd89:1:1:1-1 > > 2018-08-15 09:52:43,484 [main ] - INFO > > RequestResponseReplyToTest - CorrelationID:null > > 2018-08-15 09:52:43,484 [main ] - INFO > > RequestResponseReplyToTest - Timestamp:1534323163433 > > 2018-08-15 09:52:43,485 [main ] - INFO > > RequestResponseReplyToTest - Expiration:0 > > 2018-08-15 09:52:43,486 [main ] - INFO > > RequestResponseReplyToTest - DeliveryTime:1534323163433 > > 2018-08-15 09:52:43,486 [main ] - INFO > > RequestResponseReplyToTest - Reply-To:amqp:/_$temp.Cm8IWdyj4NAZKiy > > 2018-08-15 09:52:43,486 [main ] - INFO > > RequestResponseReplyToTest - Body:Hello world! > > 2018-08-15 09:52:43,514 [main ] - INFO > > RequestResponseReplyToTest - Request Queue Consumer Created: requests > > 2018-08-15 09:52:43,526 [main ] - INFO > > RequestResponseReplyToTest - Received request: > > 2018-08-15 09:52:43,526 [main ] - INFO > > RequestResponseReplyToTest - > > MessageID:ID:652c4867-137b-4095-a3b3-adb492f5bd89:1:1:1-1 > > 2018-08-15 09:52:43,527 [main ] - INFO > > RequestResponseReplyToTest - CorrelationID:null > > 2018-08-15 09:52:43,527 [main ] - INFO > > RequestResponseReplyToTest - Timestamp:1534323163433 > > 2018-08-15 09:52:43,527 [main ] - INFO > > RequestResponseReplyToTest - Expiration:0 > > 2018-08-15 09:52:43,527 [main ] - INFO > > RequestResponseReplyToTest - DeliveryTime:1534323163433 > > 2018-08-15 09:52:43,527 [main ] - INFO > > RequestResponseReplyToTest - Reply-To:amqp:/_$temp.Cm8IWdyj4NAZKiy > > 2018-08-15 09:52:43,527 [main ] - INFO > > RequestResponseReplyToTest - Body:Hello world! > > 2018-08-15 09:52:43,542 [main ] - INFO > > RequestResponseReplyToTest - Temporary Response Queue Producer Created: > > amqp:/_$temp.Cm8IWdyj4NAZKiy > > 2018-08-15 09:52:43,542 [main ] - INFO > > RequestResponseReplyToTest - Sending response: > > amqp:/_$temp.Cm8IWdyj4NAZKiy > > 2018-08-15 09:52:43,542 [main ] - INFO > > RequestResponseReplyToTest - MessageID:null > > 2018-08-15 09:52:43,543 [main ] - INFO > > RequestResponseReplyToTest - CorrelationID:null > > 2018-08-15 09:52:43,543 [main ] - INFO > > RequestResponseReplyToTest - Timestamp:0 > > 2018-08-15 09:52:43,543 [main ] - INFO > > RequestResponseReplyToTest - Expiration:0 > > 2018-08-15 09:52:43,543 [main ] - INFO > > RequestResponseReplyToTest - DeliveryTime:0 > > 2018-08-15 09:52:43,543 [main ] - INFO > > RequestResponseReplyToTest - Reply-To:null > > 2018-08-15 09:52:43,544 [main ] - INFO > > RequestResponseReplyToTest - Body:Hello world response! > > ----- > > The test still hangs on sending the response to the temporary queue. > > > > I have updated the test code @ > > https://github.com/fbyrne/qpid-dispatch-jms/blob/master/jms-test/src/test/java/org/apache/qpid/dispatch/jmstest/RequestResponseReplyToTest.java > > > > I would also like some more infor on why the send hangs? Are there any > > properties to control this behavior? > > Can you turn on protocol tracing, set env var PN_TRACE_FRM=1. That will > show the interaction. Acknowledgement with the router is end-to-end; the > sender will not receive an acknowledgement until the message is > acknowledged by the receiver. If it is sending to itself, then it may be > in a deadlock (it can't process the message to acknowledge it because > the sender is blocked waiting for that acknowledgement). If this is the > case, I believe setting the message to be non persistent should prevent > the send call blocking. >
Or alternatively use an asynchronous send with a CompletionListener, removing need to wait for acknowledgement during the send call. Note though that the earlier conditions would still apply as the client blocks for credit to send messages if there is none, even with async sends. Robbie --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
