[esb-issues] [JBoss JIRA] Assigned: (JBESB-855) JMSCourier does not return JMS Session to pool in jmsConnectRetry

[Mark Little (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBESB-855?page=all ]

Mark Little reassigned JBESB-855:
---------------------------------

    Assignee: Mark Little  (was: Kurt Stam)

> JMSCourier does not return JMS Session to pool in jmsConnectRetry
> -----------------------------------------------------------------
>
>                 Key: JBESB-855
>                 URL: http://jira.jboss.com/jira/browse/JBESB-855
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transports
>            Reporter: Daniel Bevenius
>         Assigned To: Mark Little
>            Priority: Critical
>             Fix For: 4.2.1
>
>
> Google group ref : http://groups.google.se/group/jbossesb/browse_frm/thread/477d6a3bca232ab2?hl=sv
> We started to see this message in our ESB server log:
> [org.jboss.internal.soa.esb.rosetta.pooling.JmsConnectionPool] The connection pool was exhausted. Waiting 1 second before trying again
> I took a look at JMSCouriers jmsConnectRetry() method and this section caught my attention:
> private void jmsConnectRetry (Exception exc)
> {
>         _logger.debug("JMS error.  Attempting JMS reconnect.", exc);
>         _jmsSession = null;
>         _messageProducer = null;
>         _messageConsumer = null;
>         ...
> }
> Should the session be returned to the pool instead of only setting it to null?
> Something like this perhaps:
> _pool.releaseSession( _jmsSession ); 
> /Daniel

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira