activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Closed) (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-1045) PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case
Date Tue, 27 Sep 2011 21:32:45 GMT

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

Timothy Bish closed AMQ-1045.
-----------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: NEEDS_REVIEWED)

The 4.x broker line is EOL.
                
> PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer
in the failure case
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1045
>                 URL: https://issues.apache.org/jira/browse/AMQ-1045
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.0
>            Reporter: Hiram Chirino
>
> 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, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message