activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-1045) PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case
Date Mon, 07 Apr 2008 22:22:32 GMT

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

David Jencks updated AMQ-1045:
------------------------------

    Fix Version/s: 4.1.3
                       (was: 4.1.2)
                       (was: 5.1.0)

Did not get fixed in 4.1.2

> 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
>            Assignee: Hiram Chirino
>             Fix For: 4.1.3
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message