Kim,

Any idea about this error?

Thanks,
Ram

On Tue, Oct 30, 2018, 2:13 PM Gordon Sim <[email protected]> wrote:

> On 30/10/18 18:59, rammohan ganapavarapu wrote:
> > There are two more error from my original post, can some one help me to
> > understand when qpid throws these error?
> >
> >
> >     1. 1. 2018-10-22 08:05:30 [Broker] error Channel exception:
> >     not-attached: Channel 0 is not attached
> >
>  
> (/builddir/build/BUILD/qpid-cpp-1.35.0/src/qpid/amqp_0_10/SessionHandler.cpp:39)
>
> The one above is comon when you are sending asynchronously, and a
> previous message caused the session to be ended with an exception frame.
> Any subsequent messages that were sent before the client received the
> exception frame result in above error.
>
> >     2. 2018-10-30 14:30:36 [Broker] error Connection exception:
> >     framing-error: Queue ax-q-axgroup-001-consumer-group-001:
> >     MessageStoreImpl::store() failed: jexception 0x0803 wmgr::enqueue()
> threw
> >     JERR_WMGR_ENQDISCONT: Enqueued new dtok when previous enqueue
> returned
> >     partly completed (state ENQ_PART). (This data_tok: id=1714315
> state=NONE)
> >
>  
> (/home/rganapavarapu/rpmbuild/BUILD/qpid-cpp-1.35.0/src/qpid/linearstore/MessageStoreImpl.cpp:1211)
> >     3. 2018-10-30 14:30:36 [Protocol] error Connection
> >     qpid.10.68.94.134:5672-10.68.94.127:39458 closed by error: Queue
> >     ax-q-axgroup-001-consumer-group-001: MessageStoreImpl::store()
> failed:
> >     jexception 0x0803 wmgr::enqueue() threw JERR_WMGR_ENQDISCONT:
> Enqueued new
> >     dtok when previous enqueue returned partly completed (state
> ENQ_PART).
> >     (This data_tok: id=1714315 state=NONE)
> >
>  
> (/home/rganapavarapu/rpmbuild/BUILD/qpid-cpp-1.35.0/src/qpid/linearstore/MessageStoreImpl.cpp:1211)(501)
>
> Not sure what the 'partly completed state' means here. Kim, any thoughts?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to