[
https://issues.apache.org/jira/browse/AMQ-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597260#comment-13597260
]
Petr Janata commented on AMQ-4139:
----------------------------------
Please reopen.
I want to attach a test case and a quick patch. It prevents connection to be
closed even when still in use.
The patch is not complete, since connection close handling should be improved:
* when {{PooledConnection.close()}} is called, all {{Sessions}} created from it
should behave like closed. It could be solved by proxying {{PooledSession}}.
* real connection failure should close all proxy connections/sessions
immediately
> Producer closed and session closed exception after upgrading to activemq
> version 5.7
> ------------------------------------------------------------------------------------
>
> Key: AMQ-4139
> URL: https://issues.apache.org/jira/browse/AMQ-4139
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.7.0
> Reporter: kalyan chakravarthi
>
> Hi,
> I have recently updated to Active MQ version 5.7 from 5.4.2, to take the
> advantage of broker redelivery. Once i have upgraded, i am facing the below
> exception.
> Exception1: Caused by: javax.jms.IllegalStateException: The producer is closed
> at
> org.apache.activemq.ActiveMQMessageProducer.checkClosed(ActiveMQMessageProducer.java:185)
> at
> org.apache.activemq.ActiveMQMessageProducerSupport.getDeliveryMode(ActiveMQMessageProducerSupport.java:148)
> at
> org.apache.activemq.pool.PooledProducer.<init>(PooledProducer.java:44)
> Exception2 :
> javax.jms.IllegalStateException: The Session is closed
> at
> org.apache.activemq.ActiveMQSession.checkClosed(ActiveMQSession.java:731)
> at
> org.apache.activemq.ActiveMQSession.rollback(ActiveMQSession.java:574)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
