On Mon, 8 Mar 2021 at 14:09, akabhishek1 <[email protected]> wrote: > > Hi Robbie, > > We got this issue again in multiple instances. We got exception stack trace > this time on "onException" block on one of instances. > > Overall Issue - Consumer is not consuming message from endpoint without > throwing any exception > > ##JMS Infrastructure## > qpid-jms-client - 56.0 > JMS connection - 1 > Exception listener - 1 > 2 listener - (8(2*4) consumers) - Every listener have 4 consumers and > sessions > (a)topic:A/subscriptions/a1 > (b)topic:B/subscriptions/b1 > 1 publisher - > > Note - every consumer/publisher have separate JMS session, MessageConsumer > and > producer > > > Impact/Action/Observations - > > 1. Depolyed Application on - 3/5/2021, 1:14:00.550 PM -- Application was > idle not receiving single messages at all > 2. Got only one "Unknown error from remote peer" error on "onException" > block, Please refer error stacktrace for more details - > https://github.com/abhikt48/servicebus/blob/master/5_march_error_for_qpid/Exception_Stack_Trace.txt > 3. Checked connection status with "isConnectionActive()" method - Connection > was active, so didn't reconnected. > 4. Checked "isConsumerActive" for first receiver(A/a1) - It was broken, so > reconnected on this receiver > 5. Checked "isConsumerActive" for first receiver(B/b1) - it was active, so > didn't reconnected > 6. Application was idle over weekend and did tested today. I published > message on both receiver and found that > (a) receiver(A/a1) - consuming msg perfectly, this was broken and > reconnected after "Unknown error from remote peer" > (b) receiver(B/b1) - not consuming messages, this was active at time > of > "Unknown error from remote peer" > > Please refer first post for implementation of "isConsumerActive" and > "isConnectionActive()" > > Application is very light and simple, which i created for testing of > ServiceBus only. Please refer below thread dump if this can help - > https://github.com/abhikt48/servicebus/blob/master/5_march_error_for_qpid/threadDump.tdump > > > Note - We have more than 100 instances running on Qpid-45, we haven't > received this type of issue in all 100+ instances. But we are facing > continuously this issue on some applications which are using Qpid-56. > > Main Issues - Whenever we got "Unknown error from remote peer" then only one > consumer got broken and other consumer status shows active for this error. > We should receive - > 1. Multiple connection exception for every receiver > 2. Or all consumer should be inactive for "Unknown error from remote peer" > > Could you please take a look on this issue and let us know for any > information. > > Regards, > Abhishek Kumar > >
The 'unknown error from peer' is identifiable from the stack as a single remote consumer closure, consistent with the resulting behaviour described. Other than that, we dont know what else actually occurred from the information. I suspect its possible the consumer sessions were each closed though. Since you have a reproducer, reproducing this with the protocol logging enabled as well would have given a much better idea, and another run with the all the regular client loggers at trace as well as the protocol logging might also have been useful. You noted having 8 consumer sessions but the thread dump only shows thread related evidence of 4, with 4 of the original sessions on the connection (i.e 1-4), presumably for the 'first listener', and another session (the 786th) evident being used for an async completion producer. That is consistent with 4 sessions being closed, or not existing, for the 'second listener'. This all appears to be on the second connection created. Having considered this and having another dig at the client, I found an issue that could be related. Though I could have sworn it did so, the client did not fire the ExceptionListener if a Session is remotely-closed while having a consumer with a MessageListener, it only did so if the consumer itself was remotely-closed. That could be a potential explanation for the behaviour you see, I have just pushed a fix for via https://issues.apache.org/jira/browse/QPIDJMS-526 that you can try out and see if it helps. Although, I would note that 0.45.0 also had the same behaviour, so it shouldn't really make a difference. > > -- > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
