qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robbie Gemmell <robbie.gemm...@gmail.com>
Subject Re: qpid-jms-client-0.45 --> Suspected deadlocked threads - owned by JmsSession delivery dispatcher
Date Tue, 22 Dec 2020 17:25:23 GMT
On Tue, 22 Dec 2020 at 16:54, akabhishek1
<mailbox.abhishek.kumar@gmail.com> wrote:
>
> I waited upto 30m still, but still application does not recived bad messages.
> After that I published one good message and application received it
> immediately.
>
> I can see that message delivery count is not increasing, it means QPID
> client is not touching to bad messages at all.

No, it really doesn't mean that. Here is the bit in your own earlier
logs showing the client getting your first 'bad message' transfer from
the server, then we know failing to get as far as firing onMessage
with it, and then the client sends a disposition explicitly telling
the server it has failed to deliver it (which is itself specifically
indicating to increment the delivery count) and also not to send it to
this same consumer (it is free to send it to others):

TRACE 2020-12-22 13:31:55,457 [AmqpProvider
:(1):[amqps://***.servicebus.windows.net:-1]]
org.apache.qpid.jms.provider.amqp.FRAMES: [994173375:1] RECV:
Transfer{handle=0, deliveryId=0,
deliveryTag=W\xb43M;ae@\xaa\x03\xefd\x94}|\xf8, messageFormat=0,
settled=null, more=false, rcvSettleMode=null, state=null,
resume=false, aborted=false, batchable=true} (5332)
"\x00Sp\xc0\x06\x05A@@@C\x00Sq\xc1$\x02\xa3\x10x-opt-lock-token\x98M3\xb4Wa;@e\xaa\x03\xefd\x94}|\xf8\x00Sr\xc1\x9e\x0c\xa3\x0ex-opt-jms-destQ\x01\xa3\x12x-opt-jms-msg-typeQ\x05\xa3\x13x-opt-enqueued-time\x83\x00\x00\x01v\x8a\xa6.\x8d\xa3\x15x-opt-sequence-numberU\x02\xa3\x1dx-opt-enqueue-sequence-numberU\x00\xa3\x12x-opt-locked-until\x83\x00\x00\x01v\x8a\xa6\xa3\xcc\x00Ss\xc0h\x0d\xa1/ID:d687d444-a096-4bb6-998b-b7cfa66c7639:1:1:1-1@\xa1\x08test@@@\xa3\x18text/plain;charset=utf-8@@\x83\x00\x00\x01v\x8a\xa6.I@@@\x00Su\xb0\x00\x00\x13\x88\xc70\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00"...(truncated)
TRACE 2020-12-22 13:31:55,552 [AmqpProvider
:(1):[amqps://***.servicebus.windows.net:-1]]
org.apache.qpid.jms.provider.amqp.FRAMES: [994173375:1] SENT:
Disposition{role=RECEIVER, first=0, last=0, settled=true,
state=Modified{deliveryFailed=true, undeliverableHere=true,
messageAnnotations=null}, batchable=false}

What the server does with the message after that, the client has no
control over. You'll have to ask Microsoft.

>
> Please find attached log.  Latest_Logs.txt
> <http://qpid.2158936.n2.nabble.com/file/t396358/Latest_Logs.txt>

Nothing to see here really. As you already said, server sends message,
application consumes it.

>
> Regards,
> Abhishek Kumar
>
>
>
> --
> Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message