qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Nachmias <michael.nachm...@gmail.com>
Subject Re: I'm using the Qpid Broker and JMS MessageConsumer times out waiting for a sync
Date Fri, 02 Dec 2016 16:53:03 GMT
Hi Gordon,

Thank you for your response. Believe I was able to figure out the problem
as it was a race condition where a queue is deleted from the broker, but
another thread attempts a close or retrieval operation on that JMS
MessageConsumer. Solution was to synchronize on the JMS MessageConsumer.


On Thu, Dec 1, 2016 at 3:46 PM, Gordon Sim <gsim@redhat.com> wrote:

> On 01/12/16 20:16, Michael Nachmias wrote:
>> We are using the C++ Broker version 1.35.0. There is an error at the same
>> time the sync timed out on the Broker:
>> Nov 29 19:37:23 dc-mb-01 qpidd[902]: 2016-11-29 19:37:23 [Broker] error
>> Execution exception: not-found: Unknown destination 192
>> session=*<edited>*@QPID.c9e6c4f7-8464-463c-9919-e77fdc0d2258
>> (/builddir/build/BUILD/qpid-cpp-1.35.0/src/qpid/broker/Seman
>> ticState.cpp:572)
> How easy is it to reproduce the error? Is it feasible to reproduce with
> protocol level tracing enabled on the broker? E.g. pass --log-enable
> notice+ --log-enable trace+:Protocol to qpidd when starting?
> That would provide a bit more context. The error suggests that some
> operation was attempted on a consumer that the broker did not think existed.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message