-
Bug
-
Resolution: Won't Do
-
Minor
-
EAP 6.0.0
-
None
-
NEW
The exception "Authentication failed" is printed out but the client connects successfully. This occurs when you run HA profile (standalone-ha.xml) and when ApplicationRealm is defined on remoting and the client has to be run from other machine than the jboss server is placed.
Then the following exception is printed in console but the remote connection works fine.
Jun 4, 2012 4:58:49 PM org.jboss.ejb.client.remoting.VersionReceiver handleMessage INFO: EJBCLIENT000017: Received server version 1 and marshalling strategies [river] Jun 4, 2012 4:58:49 PM org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver associate INFO: EJBCLIENT000013: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@b03be0, receiver=Remoting connection EJB receiver [connection=Remoting connection <e64686>,channel=jboss.ejb,nodename=1011server3]} on channel Channel ID d30e5113 (outbound) of Remoting connection 016d2633 to /192.168.56.101:4447 Jun 4, 2012 4:58:49 PM org.jboss.remoting3.remote.RemoteConnection handleException ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed Jun 4, 2012 4:58:49 PM org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager getEJBReceiver INFO: Could not create a connection for cluster node ClusterNode{clusterName='ejb', nodeName='1011server3', clientMappings=[ClientMapping{sourceNetworkAddress=/0:0:0:0:0:0:0:0, sourceNetworkMaskBits=0, destinationAddress='192.168.56.101', destinationPort=4447}], resolvedDestination=[Destination address=192.168.56.101, destination port=4447]} in cluster ejb java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:91) at org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager.getEJBReceiver(RemotingConnectionClusterNodeManager.java:104) at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:406) at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:380) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:315) at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:214) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189) at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) at org.xnio.nio.NioHandle.run(NioHandle.java:90) at org.xnio.nio.WorkerThread.run(WorkerThread.java:184) at ...asynchronous invocation...(Unknown Source) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:386) at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:151) at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:132) at org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager.getEJBReceiver(RemotingConnectionClusterNodeManager.java:101) ... 7 more
I have tested this with my following ejb properties:
https://github.com/ochaloup/testing/blob/master/myejbclient/src/jboss-ejb-client.properties
