[ https://issues.apache.org/jira/browse/AMQ-4366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619630#comment-13619630 ]
Torsten Mielke commented on AMQ-4366: ------------------------------------- A proper workaround for any 5.7 and 5.8 versioned clients seems to be to disable the session idle timeout on the ConnectionFactory using PooledConnectionFactory.setIdleTimeout(0). > PooledConnectionFactory closes connections that are in use > ---------------------------------------------------------- > > Key: AMQ-4366 > URL: https://issues.apache.org/jira/browse/AMQ-4366 > Project: ActiveMQ > Issue Type: Bug > Components: activemq-pool > Affects Versions: 5.7.0, 5.8.0 > Reporter: Petr Janata > Assignee: Timothy Bish > Fix For: 5.9.0 > > Attachments: poolConClose.diff > > > {{PooledConnectionFactory}} closes connections that are still referenced and > should not be closed. Happens only when connection idle or expire time > passes. Calling {{createConnection}} after that time will invalidate the > connection and all previously obtained {{Sessions}} will behave as closed. > Due to default 30 second idle timeout, it is likely not to cause problems > when: > * connection is continually in use > * all {{PooledConnection}}s are borrowed at startup > Client with session whose connection was prematurely closed will see similar > stacktrace: > {noformat} > javax.jms.IllegalStateException: The Session is closed > at > org.apache.activemq.ActiveMQSession.checkClosed(ActiveMQSession.java:731) > at > org.apache.activemq.ActiveMQSession.configureMessage(ActiveMQSession.java:719) > at > org.apache.activemq.ActiveMQSession.createBytesMessage(ActiveMQSession.java:316) > at > org.apache.activemq.pool.PooledSession.createBytesMessage(PooledSession.java:168) > {noformat} -- 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