activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-1045) PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case
Date Tue, 14 Nov 2006 14:14:02 GMT
     [ https://issues.apache.org/activemq/browse/AMQ-1045?page=all ]

Hiram Chirino resolved AMQ-1045.
--------------------------------

    Resolution: Fixed

Fixed in trunk rev 474799 and in 4.1 branch rev 474800

> PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer
in the failure case
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1045
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1045
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.0
>            Reporter: Hiram Chirino
>         Assigned To: Hiram Chirino
>             Fix For: 4.1.1, 4.2.0
>
>
> The DefaultMessageListenerContainer has retry logic built into it. When a connection
dies it tried to reconnect by getting a new connection from the ConnectionFactory. Since the
PooledConenctionFactory has one Connection it, it keeps on trying to give out the Connection
that died. We would like the PooledConnectionFactory to be able to "evict" the dead connection
and create a new one.

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

        

Mime
View raw message