[jboss-jira] [JBoss JIRA] (AS7-5769) " Remote connection failed: javax.security.sa sl.SaslException: Authentication failed: all available authentication mechanisms" failed appears randomally
Alexey S. (JIRA)
jira-events at lists.jboss.org
Wed Oct 17 09:00:04 EDT 2012
[ https://issues.jboss.org/browse/AS7-5769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727215#comment-12727215 ]
Alexey S. commented on AS7-5769:
--------------------------------
Please let me to disagree. What can prove it? What do you need for proof? It seems that under some conditions separated stateless invocations are working partially.
> " Remote connection failed: javax.security.sa sl.SaslException: Authentication failed: all available authentication mechanisms" failed appears randomally
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-5769
> URL: https://issues.jboss.org/browse/AS7-5769
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.1.Final
> Environment: windows
> Reporter: Alexey S.
> Assignee: jaikiran pai
> Priority: Critical
> Labels: as7, remote-ejb-connection, security
>
> Hello everybody and JBoss guys.
>
> Very simple and critical issue.
>
> Our system runs Grails app which is an EJB Client.
> Randomally it gots
> [Remoting "config-based-ejb-client-endpoint" read-1] ERR
> OR remote.connection - JBREM000200: Remote connection failed: javax.security.sa
> sl.SaslException: Authentication failed: all available authentication mechanisms
> failed
> java.lang.IllegalStateException: No EJB receiver available for handling blablabla.
>
> Just to make myself clear- same code, same place, same connection, everything is reproducable when client and server are on the same PC: sometimes EJB invocation works and sometimes raises this "
> [Remoting "config-based-ejb-client-endpoint" read-1] ERR
> OR remote.connection - JBREM000200: Remote connection failed: javax.security.sa
> sl.SaslException: Authentication failed: all available authentication mechanisms
> failed
> java.lang.IllegalStateException: No EJB receiver available for handling blablabla.
>
>
> Seems this is a showstopper issue, what do you think about?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list