I was check the code and i see these lines for that AIO timeout.
case qpid::linearstore::journal::RHM_IORES_PAGE_AIOWAIT:
if (++aio_sleep_cnt > MAX_AIO_SLEEPS)
THROW_STORE_EXCEPTION("Timeout waiting for AIO in
MessageStoreImpl::recoverMessages()");
Actually we have upgraded from qpid-cpp 0.28 to 1.35 and after that we see
this message
2018-10-27 18:58:25 [Store] warning Linear Store: Journal "":
Bad record alignment found at fid=0x4605b offs=0x107680 (likely journal
overwrite boundary); 19 filler record(s) required.
2018-10-27 18:58:25 [Stor
No, local disk.
On Mon, Nov 5, 2018 at 3:26 PM Gordon Sim wrote:
> On 05/11/18 22:58, rammohan ganapavarapu wrote:
> > Gordon,
> >
> > We are using java client 0.28 version and qpidd-cpp 1.35 version
> > (qpid-cpp-server-1.35.0-1.el7.x86_64), i dont know at what scenario its
> > happening but af
On 05/11/18 22:58, rammohan ganapavarapu wrote:
Gordon,
We are using java client 0.28 version and qpidd-cpp 1.35 version
(qpid-cpp-server-1.35.0-1.el7.x86_64), i dont know at what scenario its
happening but after i restart broker and if we wait for few days its
happening again. From the above lo
Gordon,
We are using java client 0.28 version and qpidd-cpp 1.35 version
(qpid-cpp-server-1.35.0-1.el7.x86_64), i dont know at what scenario its
happening but after i restart broker and if we wait for few days its
happening again. From the above logs do you have any pointers to check?
We are usin
On 05/11/18 20:57, rammohan ganapavarapu wrote:
Actually there are no messages in queue, all they messages got consumed by
consumer.
But it still will not enqueue any further messages? Can you reproduce
this easily?
One other suggestion is to try with the linear store rather than the
legacy
I also see this in qpidd logs for broker,store and protocol. Please help me
to understand what it means? why i am i getting "Timeout waiting for AIOs
to complete" ? does it means some thing wrong with journal files?
2018-02-28 13:19:00 [Store] critical Journal "q-001": get_events() returned
JERR_J
Actually there are no messages in queue, all they messages got consumed by
consumer. I also observe two tcp connections to each client and for this
client only one tcp connection. Why does qpid creates two connections?
Ram
On Mon, Nov 5, 2018, 11:09 AM Gordon Sim Can you drain the queue?
>
> ---
Can you drain the queue?
-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
I am using java client version 0.28 and qpid-cpp 1.35 version, and i see
this error on client side(producer).
2018-11-02 00:00:46,376 IoSender - /1.2.3.4:5672 INFO
o.a.q.t.n.io.IoSender - Logger.info() : Exception in thread sending to '/
1.2.3.4:5672': java.net.SocketException: Broken pipe (Write
On Sat, Nov 3, 2018 at 6:32 PM Chuck Rolke wrote:
> Hi basavaraj,
>
> The issue here is that the broker wants to negotiate a SASL layer but the
> Proton C++ example is skipping that during connection startup. AMQP allows
> startup options SASL and TLS before jumping into an AMQP session. SASL
> p
11 matches
Mail list logo
