You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2010/01/16 21:20:43 UTC

[jira] Closed: (AMQ-1608) diagnostics: "Waiting for transport to reconnect" where?

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

Timothy Bish closed AMQ-1608.
-----------------------------

    Resolution: Working as Designed

The point at which this is logged there is no current URI to log, the code logs the URI its trying to connect to in the reconnect method which should be sufficient for debug purposes.

{noformat}
                            LOG.debug("Attempting connect to: " + uri);
{noformat}

> diagnostics: "Waiting for transport to reconnect" where?
> --------------------------------------------------------
>
>                 Key: AMQ-1608
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1608
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Transport
>    Affects Versions: 5.0.0
>            Reporter: Stepan Koltsov
>             Fix For: 5.4.0
>
>
> Have messages in log:
> {code}
> DEBUG  [org.apache.activemq.transport.failover.FailoverTransport] Waiting for transport
>     to reconnect.
> {code}
> This line should contain connect URL, like:
> {code}
> DEBUG  [org.apache.activemq.transport.failover.FailoverTransport] Waiting for transport
>     to reconnect to failover:tcp://localhost:12345
> {code}
> to make diagnostics easier.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.