[jboss-jira] [JBoss JIRA] (JGRP-2227) Use of AUTH does not result in a SecurityException, but instead nodes create separate clusters with the same name

[Bela Ban (JIRA)]

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

Bela Ban commented on JGRP-2227:
--------------------------------

Perhaps the members don't find each other? If B starts and doesn't find A in the discovery process, then of course no exception will be thrown.
I suggest setting a breakpoint in {{JChannel._connect(Event evt)}}, to see what's going on. Also, if you enable trace logging of {{GMS}} and your discovery protocol (e.g. {{PING}}), you'll see whether B discovers A, or not.

> Use of AUTH does not result in a SecurityException, but instead nodes create separate clusters with the same name
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: JGRP-2227
>                 URL: https://issues.jboss.org/browse/JGRP-2227
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 4.0.6
>            Reporter: Robert Cernak
>            Assignee: Bela Ban
>             Fix For: 4.0.12
>
>         Attachments: jgroupsDoesNotThrowSecurityExceptionWithJgroups4012.zip, jgroupsLogs.zip
>
>
> I implemented method org.jgroups.auth.AuthToken#authenticate(AuthToken token, Message msg) in my class and its body contained only one line: return false; 
> In this way authentication should be false and I should get SecurityException.
> When I started joining of nodes together to form a cluster, instead of getting SecurityException, nodes formed 2 different clusters with the same name.
> I am sure method was evaluated, since I tried to run it also with breakpoint, which was triggered during joining process.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)