Hi Michael, Which Broker (Java/C++) are you using? Is there anything in the broker logs indicating an issue at the time where these errors are occurring?
-- Rob On 1 December 2016 at 17:22, Michael Nachmias <michael.nachm...@gmail.com> wrote: > Hello, > > I'm running a enterprise Java web application using Java jdk 1.7.0.101, > Qpid 0.30, and JMS 1.1. I'm running into intermittent issues where closing > or retrieving from the JMS MessageConsumer times out waiting for a sync. > The following is the stack trace of the exception: > > 2016-11-29 19:38:23,791 DEBUG [org.apache.qpid.client.AMQConnection] > (ajp-/10.1.15.14:8009-21) exceptionReceived done by:ajp-/10.1.15.14:8009 > -21: > org.apache.qpid.AMQException: timed out waiting for sync: complete = 23136, > point = 23141 [error code 541: internal error] > at org.apache.qpid.client.AMQSession_0_10.setCurrentException( > AMQSession_0_10.java:1081) > [qpid-client-0.30.jar:0.30] > at org.apache.qpid.client.BasicMessageConsumer_0_10.sendCancel( > BasicMessageConsumer_0_10.java:175) [qpid-client-0.30.jar:0.30] > at org.apache.qpid.client.BasicMessageConsumer.close( > BasicMessageConsumer.java:613) > [qpid-client-0.30.jar:0.30] > at org.apache.qpid.client.BasicMessageConsumer.close( > BasicMessageConsumer.java:573) > [qpid-client-0.30.jar:0.30] > > Is there any way to determine what is the root cause of this or if this has > been addressed in an updated version of Qpid/JMS? Thank you for your help. >
