activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-3066) Subscriptions not refreshed following re-connection on a duplex link
Date Fri, 01 Feb 2013 21:48:12 GMT

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

Timothy Bish closed AMQ-3066.
-----------------------------

    Resolution: Incomplete

No test code provided to validate.  Please test against a newer broker release and report
back with a JUnit test if your issue still persists. 
                
> Subscriptions not refreshed following re-connection on a duplex link
> --------------------------------------------------------------------
>
>                 Key: AMQ-3066
>                 URL: https://issues.apache.org/jira/browse/AMQ-3066
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.4.1
>         Environment: Running ActiveMQ 5.4.1 on RHEL 5.4.
>            Reporter: Carl Cranidge
>
> We have ActiveMQ set up in  hub and spoke topology which for security reasons is configured
using duplex connections initiated from the hub.  We upgraded to 5.4.1 as we were seeing loss
of subscriptions when a connection was lost and re-established using a static failover transport
with a single defined connection.  
> Since the upgrade we have seen an improvement.  When a connection is re-established the
subscriptions on the remote end are re-established within the hub, but the subscriptions within
the hub are not re-established on the remote end of the connection.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message