activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (AMQ-1771) Failover transport should always signal resume of transport
Date Thu, 05 Jun 2008 18:13:00 GMT

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

rajdavies edited comment on AMQ-1771 at 6/5/08 11:12 AM:
----------------------------------------------------------

Fixed by SVN revision 663680 and 663691

      was (Author: rajdavies):
    Fixed by SVN revision 663680
  
> Failover transport should always signal resume of transport
> -----------------------------------------------------------
>
>                 Key: AMQ-1771
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1771
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.1.0
>         Environment: WinXP, JDK5
>            Reporter: Andreas Kuhtz
>            Assignee: Rob Davies
>             Fix For: 5.2.0
>
>         Attachments: amq-failover.patch
>
>
> The FailoverTransport does currently not signal the initial resume of the transport (due
to race condition) nor the failure (if maxReconnectAttempts is 0) and therefore we don't know
if the connection is successfully connected or not.
> The attached patch adds a sleep (copied from the failure processing part some lines below)
that ensures that the ??transportListener?? is set and the ??transportListener.transportResumed()??
is called.

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