[
https://issues.jboss.org/browse/JGRP-1274?page=com.atlassian.jira.plugin....
]
Bela Ban updated JGRP-1274:
---------------------------
Workaround Description: (was: - Nodes A and B (remove FD or FD_ALL from config, only
leave FD_SOCK)
- A sends unicast mesages to B
- Suspend B (ctrl-z)
- Have A send unicast messages to B until A blocks (B doesn't send credit responses
back to A because it is suspended)
- Kill -9 B
==> A won't unblock on the view change !
This is because on UFC line 115ff, the loop doesn't check for presence or absence of
the target node)
Steps to Reproduce:
- Nodes A and B (remove FD or FD_ALL from config, only leave FD_SOCK)
- A sends unicast mesages to B
- Suspend B (ctrl-z)
- Have A send unicast messages to B until A blocks (B doesn't send credit responses
back to A because it is suspended)
- Kill -9 B
==> A won't unblock on the view change !
This is because on UFC line 115ff, the loop doesn't check for presence or absence of
the target node
UFC: leaving or crashing of target node doesn't unblock sender
--------------------------------------------------------------
Key: JGRP-1274
URL:
https://issues.jboss.org/browse/JGRP-1274
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.11.1, 2.12
When we have A and B, and A is blocked due to credits on B, and B subsequently leaves or
crashes, A won't unblock
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira