activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Petr Janata (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-4366) PooledConnectionFactory closes connections that are in use
Date Tue, 02 Apr 2013 09:09:15 GMT

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

Petr Janata updated AMQ-4366:
-----------------------------

    Description: 
{{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}



  was:
{{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}



    
> 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

Mime
View raw message