activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "kurt (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1045) PooledConnectionFactory does not work with the org.springframework.jms.listener.DefaultMessageListenerContainer in the failure case
Date Thu, 16 Jul 2009 15:20:34 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52848#action_52848
] 

kurt commented on AMQ-1045:
---------------------------

PooledConnectionFactory does not deal with pooling of consumers; for that look at a library
like Jencks

> 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
>             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