Bug 1028411

Summary:	Make client side Connection refused error TRACE
Product:	[JBoss] JBoss Data Grid 6	Reporter:	Michal Linhard <mlinhard>
Component:	Infinispan	Assignee:	Galder Zamarreño <galder.zamarreno>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nobody <nobody>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.5.0	CC:	jdg-bugs, mgencur, nobody, slaskawi, vjuranek
Target Milestone:	ER3
Target Release:	6.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-23 12:24:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.