If you have exceptions then please provide the stacktraces, it may
contain context helpful in itself which the messages doesnt
(particularly when the exception message appears to be, the peer did
not specify an error message).
There haven't been many significant changes since 0.45.0 I would
expect could alter behaviour in this space. Most or all of those were
made to address bugs or change behaviours identified from your reports
both with 0.45.0 and subsequent releases.
Its difficult to reason much at all from the information available, however...
There are a variety of ways I might not expect to receive an exception
in the listener upon detaching, such as if the error was already
reported (something did, unclear what from the minimal
detail...posting the rest more may or may not make it clearer), or the
resource was previously / is currently being attempted to be locally
closed, or the parent session / connection was closed (which naturally
implicitly closes their children, but doesnt provoke a storm of
related exceptions), and i'm sure there are others.
You may also have blocked the thread again somehow, as has happened
before in your use case, perhaps stopping further issues being
communicated.
You also previously reported unexpected 'disabling subscription'
behaviour as a client bug, whereby 0.56.0 reported the very exceptions
you are now indicating it didnt, when really it was the server that
just didnt do what you expected, perhaps that is true here as well?
We do have a test that shows the client fires the exception listener
when a consumer with listener is remotely closed, though it's
certainly possible your somewhat more elaborate use case is getting
into a corner case, but I dont immediately see one, and again not much
has changed in those areas.
It's of course worth adding the obvious, that while a consumer not
receiving messages could indeed indicate an issue with it, it doesn't
necessarily. It may just not have been given any.
Robbie
On Wed, 17 Feb 2021 at 08:52, akabhishek1
<mailbox.abhishek.ku...@gmail.com> wrote:
>
> Hi Team,
>
> We recently upgraded qpid-jms-client to 56.0. We are using qpid-jms-client
> ti receive message from ServiceBus. We need your urgent support on this
> issue, because we are facing this issue in PROD environment.
>
> Issue - Some consumers are not receiving message from queue without any
> connection failure and detached receiver error
>
> JMS Infrastructure -
> JMS connection - 1
> Exception listener - 1
> 7 destination (Queue/topic) - every destination has 4 consumers
> 28 consumers - every consumer have separate JMS session and MessageConsumerr
>
> Scenario -
> 1. Received only one below error on "onException" block -
>
> Connection exception from 'ServiceBus_Connector', isConnectionActive 'true',
> Reason 'Unknown error from remote peer' - 'class javax.jms.JMSException',
> cause 'org.apache.qpid.jms.provider.ProviderException: Unknown error from
> remote peer'
>
> 2. As connection is active, so we didn't establish re-connection. We checked
> connection status with below method
> 3. Checked receiver status with below isConsumerActive method and found that
> only reciever is closed, so re-established receiver and this consumer is
> consuming messages perfectly.
>
> Impact - 1. One consumer receiving message perfectly
> 2. Six consumer does not throw any connection error, or detached
> error
> 3. These six consumers stopped receiving message from queue
>
> Could you please urgently suggest your opinion on this issue ?
>
>
> public boolean isConnectionActive(Connection connection) {
> boolean connectionStatus = false;
> try {
> String clientID = connection.getClientID();
> connectionStatus = true;
> } catch (Exception e) {
> connectionStatus = false;
> }
> return connectionStatus;
> }
>
> public boolean isConsumerActive(MessageConsumer consumer) {
> boolean isConsumerActive = false;
> try {
> consumer.getMessageListener();
> isConsumerActive = true;
> } catch (Exception e) {
> isConsumerActive = false;
> }
> return isConsumerActive;
> }
>
>
> Regards,
> Abhishek Kumar
>
>
>
> --
> Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
