-
Bug
-
Resolution: Done
-
Critical
-
3.3.1.Final
-
None
After creating JBIDE-12351 for JMX connection, I found out that the connection cannot be established at all - even when you don't try to connect via JMX.
When you set up a remote as7/eap6 server accessible over IPv6 and start the server, the remote connection will fail with this error:
Jul 20, 2012 3:14:57 PM org.xnio.Xnio <clinit> INFO: XNIO Version 3.0.3.GA Jul 20, 2012 3:14:57 PM org.xnio.nio.NioXnio <clinit> INFO: XNIO NIO Implementation Version 3.0.3.GA Jul 20, 2012 3:14:57 PM org.jboss.remoting3.EndpointImpl <clinit> INFO: JBoss Remoting version 3.2.7.GA Jul 20, 2012 3:15:46 PM org.jboss.remoting3.remote.RemoteConnection handleException ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed Jul 20, 2012 3:15:46 PM org.jboss.remoting3.remote.RemoteConnection handleException ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed Jul 20, 2012 3:15:51 PM org.xnio.Xnio <clinit> INFO: XNIO Version 3.0.4.GA-redhat-1 Jul 20, 2012 3:15:51 PM org.xnio.nio.NioXnio <clinit> INFO: XNIO NIO Implementation Version 3.0.4.GA-redhat-1 Jul 20, 2012 3:15:51 PM org.jboss.remoting3.EndpointImpl <clinit> INFO: JBoss Remoting version 3.2.8.GA-redhat-1 Jul 20, 2012 3:15:52 PM org.jboss.remoting3.remote.RemoteConnection handleException ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
- relates to
-
JBIDE-12351 JMX connection to servers cannot be established with IPv6
-
- Closed
-