[
http://jira.jboss.com/jira/browse/JGRP-577?page=all ]
Bela Ban reopened JGRP-577:
---------------------------
[mail by Brian Campbell]
These logs were produced as follows:
Server A comes up first and stays up the whole time. B comes up with
the wrong credentials and, the first time, gets the join rejection/auth
failure message from A and throws the SecurityException on its side. I
ctrl-c kill B. Then start B again and it falls into the join timeout
loop. Ctrl-C will no longer stop the process so I have to kill -9 it.
Finally I start B one more time - this time with the correct credentials
and it ends up in a similar join timeout loop.
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.6, 2.5.1
Attachments: a.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