[jboss-jira] [JBoss JIRA] (JGRP-1556) Incorrect error log message in RequestCorrelator

RH Bugzilla Integration (JIRA) jira-events at lists.jboss.org
Wed Jan 9 09:09:08 EST 2013


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

RH Bugzilla Integration commented on JGRP-1556:
-----------------------------------------------

Tristan Tarrant <ttarrant at redhat.com> changed the Status of [bug 888429|https://bugzilla.redhat.com/show_bug.cgi?id=888429] from NEW to MODIFIED
                
> Incorrect error log message in RequestCorrelator
> ------------------------------------------------
>
>                 Key: JGRP-1556
>                 URL: https://issues.jboss.org/browse/JGRP-1556
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 3.2.4
>            Reporter: Michal Linhard
>            Assignee: Bela Ban
>            Priority: Minor
>             Fix For: 3.2.6, 3.3
>
>
> I have this when running JDG 6.1.0.ER6 with JGroups 3.2.4
> {code}
> 08:31:41,460 ERROR [org.jgroups.blocks.RequestCorrelator] failed sending rsp: return value (SuccessfulResponse{responseValue=null} ) is not serializable
> {code}
> which is of course not the cause of the error.
> This message is logged when any Throwable is caught
> https://github.com/belaban/JGroups/blob/26b7c60d511baf199674b45d3d402dfbbc667e9e/src/org/jgroups/blocks/RequestCorrelator.java#L509
> in my case it was once NullPointerException and once InterruptedException probably caused by caches and externalizers shutting down.
> I'd recommend rewording of the message if the exception is not NotSerializableException or the like to avoid confusion.

--
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


More information about the jboss-jira mailing list