You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (Jira)" <ji...@apache.org> on 2021/11/10 11:32:00 UTC

[jira] [Closed] (QPIDJMS-520) Exception when closing JMS sessions with a simple client. Connection blocked after error.

     [ https://issues.apache.org/jira/browse/QPIDJMS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell closed QPIDJMS-520.
----------------------------------
    Resolution: Information Provided

> Exception when closing JMS sessions with a simple client. Connection blocked after error.
> -----------------------------------------------------------------------------------------
>
>                 Key: QPIDJMS-520
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-520
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>    Affects Versions: 0.54.0
>            Reporter: Shaan Jayaratna
>            Priority: Critical
>         Attachments: qpid-close-timeout.zip
>
>
> Hi Dev Team,
> i wrote a small example Maven program to demonstrate the issue. It simply opens and closes jms sessions. On the x-th iteration the close operation failes with the following Exception:
> ****************************
> Exception in thread "main" org.apache.qpid.jms.JmsOperationTimedOutException: Timed Out Waiting for close response: AmqpSession \{ ID:f41c6018-f5a6-4be0-a880-a3405a091e18:1:4697 }Exception in thread "main" org.apache.qpid.jms.JmsOperationTimedOutException: Timed Out Waiting for close response: AmqpSession \{ ID:f41c6018-f5a6-4be0-a880-a3405a091e18:1:4697 } at org.apache.qpid.jms.provider.exceptions.ProviderOperationTimedOutException.toJMSException(ProviderOperationTimedOutException.java:39) at org.apache.qpid.jms.provider.exceptions.ProviderOperationTimedOutException.toJMSException(ProviderOperationTimedOutException.java:25) at org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:80) at org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:112) at org.apache.qpid.jms.JmsConnection.destroyResource(JmsConnection.java:761) at org.apache.qpid.jms.JmsConnection.destroyResource(JmsConnection.java:745) at org.apache.qpid.jms.JmsSession.doClose(JmsSession.java:306) at org.apache.qpid.jms.JmsSession.close(JmsSession.java:292) at example.OpenClose.main(OpenClose.java:31)
> ****************************
> If i catch the exception and ignore it, than the program will hang, when it tries to create another session on the same connection.
> Is this an intended behaviour? How should i close the session the proper way?
> I used: 
> RabbitMq 3.8.9 with only one Plugin: rabbitmq_amqp1_0
> ->Erlang 23.1
> Qpid 0.54.0
> ->Java 1.8
> Kind Regards
> Shaan



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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