[
https://jira.jboss.org/browse/JGRP-1237?page=com.atlassian.jira.plugin.sy...
]
vivek v updated JGRP-1237:
--------------------------
Description:
This is the issue with JGroups 2.10 GA when using Tunnel with multiple Gossip Routers. In
our case the nodes start sequentially. Two of the nodes have Gossip Router running. As
each node is configured to talk to two GR via Tunnel, the first one starting always throws
a big stacktrace when not able to connect to the second GR. We don't need to print the
stacktrace when failed to connect to other GRs - we can simply put the warning with
stacktrace.
File: Tunnel.java
Line: 421 (inside connect method)
[code]
catch (Exception e) {
if (log.isWarnEnabled())
log.warn("Failed connecting to GossipRouter at " +
stub.getGossipRouterAddress()); //no stacktrace
stubManager.startReconnecting(stub);
}
[code]
was:
This is the issue with JGroups 2.10 GA when using Tunnel with multiple Gossip Routers. In
our case the nodes start sequentially. Two of the nodes have Gossip Router running. As
each node is configured to talk to two GR via Tunnel, the first one starting always throws
a big stacktrace when not able to connect to the second GR. We don't need to print the
stacktrace when failed to connect to other GRs - we can simply put the warning with
stacktrace.
File: Tunnel.java
Line: 421 (inside connect method)
{noformat}
catch (Exception e) {
if (log.isWarnEnabled())
log.warn("Failed connecting to GossipRouter at " +
stub.getGossipRouterAddress()); //no stacktrace
stubManager.startReconnecting(stub);
}
{noformat}
Remove print stacktrace from Tunnel warning when backup gossip router
is not available
---------------------------------------------------------------------------------------
Key: JGRP-1237
URL:
https://jira.jboss.org/browse/JGRP-1237
Project: JGroups
Issue Type: Bug
Affects Versions: 2.10
Environment: Linux, JGroups 2.10 GA
Reporter: vivek v
Assignee: Bela Ban
This is the issue with JGroups 2.10 GA when using Tunnel with multiple Gossip Routers. In
our case the nodes start sequentially. Two of the nodes have Gossip Router running. As
each node is configured to talk to two GR via Tunnel, the first one starting always throws
a big stacktrace when not able to connect to the second GR. We don't need to print the
stacktrace when failed to connect to other GRs - we can simply put the warning with
stacktrace.
File: Tunnel.java
Line: 421 (inside connect method)
[code]
catch (Exception e) {
if (log.isWarnEnabled())
log.warn("Failed connecting to GossipRouter at " +
stub.getGossipRouterAddress()); //no stacktrace
stubManager.startReconnecting(stub);
}
[code]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira