[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

[Bela Ban (JIRA)]

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

Bela Ban commented on JGRP-1428:
--------------------------------

After the request is created, even if it misses the new view installed at the same time the request is added, it will get called viewChange(), so its membership should be correct. After this, view change notifications will be handled the normal way.

Can you show me a timing scenario which causes a request to have an incorrect target set ?
                
> 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.6, 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