You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2006/11/14 15:12:02 UTC
[jira] Updated: (AMQ-1045) PooledConnectionFactory does not work
with the org.springframework.jms.listener.DefaultMessageListenerContainer
in the failure case
[ https://issues.apache.org/activemq/browse/AMQ-1045?page=all ]
Hiram Chirino updated AMQ-1045:
-------------------------------
Description: 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.
> 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.2.0, 4.1.1
>
>
> 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