[
http://jira.jboss.com/jira/browse/JGRP-577?page=comments#action_12373105 ]
Bela Ban commented on JGRP-577:
-------------------------------
This was caused by UNICAST which created a Connection for B on the first (failed) JOIN.
Subsequent JOINs failed because that connection was not removed on the failed JOIN, so A
incorrectly used the old connection.
Fixed in CVS head (2.6) and 2.5.1
AUTH: join rejection won't be received because UNICAST drops it
---------------------------------------------------------------
Key: JGRP-577
URL:
http://jira.jboss.com/jira/browse/JGRP-577
Project: JGroups
Issue Type: Bug
Affects Versions: 2.5
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.5.1, 2.6
Attachments: a.log, b.log
When AUTH processes a JOIN request and rejects it, it sends back a unicast message to the
joiner. However, that message is dropped by UNICAST as the destination is not in the
membership !
SOLUTION: use Event.ENABLE_UNICASTS_TO before sending the rejection. (This works in TCP
as there is no UNICASR protocol in TCP)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira