[jboss-jira] [JBoss JIRA] (JGRP-1428) UnicastRequest and GroupRequest should mark a target as suspected if the target has already left the cluster at creation time

[RH Bugzilla Integration (JIRA)]

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

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

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

Another confirmation of this is 4node elasticity test on hyperion:
http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-QE/job/edg-60-resilience-log-analysis/31/artifact/table.html
http://www.qa.jboss.com/~mlinhard/hyperion/run27-elasticity4/report/stats-throughput.png
                
> UnicastRequest and GroupRequest should mark a target as suspected if the target has already left the cluster at creation time
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JGRP-1428
>                 URL: https://issues.jboss.org/browse/JGRP-1428
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 3.0.5, 3.1
>            Reporter: Dan Berindei
>            Assignee: Bela Ban
>            Priority: Critical
>             Fix For: 3.0.7, 3.1
>
>
> UnicastRequest and GroupsRequest both detect if a target has left the cluster and mark its response as "suspected".
> However, if the node has already left the cluster by the time the request is created, its response is not marked as "suspected" and the request never properly finishes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira