Do I need to post my client code to get an answer to this?
I can reproduce that at any time quite easily. It happens continuously
while the client is running. A little less than 1% of the total number of
messages end up not showing Dequeued but they are actually being processed
and ack'd.
The "Di
I am trying to write a topic consumer that is as robust as possible to
virtually all errors.
So far, so goodbut now I've hit an error that's not mine and appears to
be inside the receive chain.
The connection is client ack which I think is what caused this problem.
session = conn.createTopi
I figured this was a common problem as there are tons of google references
but none for just a simple client (all seem to be3rd party apps with 3rd
party fixes to it).
tcp://10.2.100.209:61616?keepAlive=true
I don’t have access to the broker config – as I said – no control over it.
Broker is Act
Broker: localhost - Client: mblack3 already connected from
tcp://10.40.245.19:4688
I'm trying to make my client as robust as possible so I'm testing crashes at
different stages of processing.
This is the one thing that's slowing down developing this a lot. When the
client crashes the subscriptio
