[infinispan-issues] [JBoss JIRA] (ISPN-3691) Make client side Connection refused error TRACE

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925671#comment-12925671 ] 

RH Bugzilla Integration commented on ISPN-3691:
-----------------------------------------------

Michal Linhard <mlinhard at redhat.com> made a comment on [bug 1028411|https://bugzilla.redhat.com/show_bug.cgi?id=1028411]

still in 6.2.0.ER4
                
> Make client side Connection refused error TRACE
> -----------------------------------------------
>
>                 Key: ISPN-3691
>                 URL: https://issues.jboss.org/browse/ISPN-3691
>             Project: Infinispan
>          Issue Type: Feature Request
>    Affects Versions: 6.0.0.CR1
>            Reporter: Michal Linhard
>            Assignee: Mircea Markus
>            Priority: Minor
>
> After solving ISPN-3454, it seems that only remaining client-side error during node crashes is "Connection refused":
> 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
> This has been reported before as ISPN-1794 or ISPN-1119, but actually it seems like it reappeared in different place.
> Sorry for not reporting sooner, I got used to ignoring some of the long-open cosmetic low-prio log message issues, that I forgot about this one...
> 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

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira