Bug 1028411 - Make client side Connection refused error TRACE
Summary: Make client side Connection refused error TRACE
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ER3
: 6.5.0
Assignee: Galder Zamarreño
QA Contact: Nobody
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-08 11:45 UTC by Michal Linhard
Modified: 2015-06-23 12:24 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-23 12:24:47 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-3691 0 Minor Resolved Make client side Connection refused error TRACE 2017-12-07 07:12:35 UTC

Description Michal Linhard 2013-11-08 11:45:04 UTC 
see https://issues.jboss.org/browse/ISPN-3691

error message example:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/RESILIENCE/job/jdg-func-resilience-dist-4-3/97/artifact/report/loganalysis/client/categories/cat10_entry0.txt


The issue here is that these "Connection refused" problems are retry-able, so the client log shouldn't contain error.
Maybe only some info level message about failing over to different node. But that's actually already reported by the INFO level messages about the topology changes
Comment 2 Michal Linhard 2013-11-21 10:35:50 UTC 
still in 6.2.0.ER4
Comment 5 JBoss JIRA Server 2015-04-27 16:23:03 UTC 
Galder Zamarreño <galder.zamarreno> updated the status of jira ISPN-3691 to Resolved
Comment 6 Galder Zamarreño 2015-04-28 07:35:36 UTC 
I've backported the fix to 6.5.x and changed the version of this BZ.
Note You need to log in before you can comment on or make changes to this bug.