Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-12352

Remote management connection to servers cannot be established with IPv6

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 3.3.1.Final
    • Fix Version/s: 4.3.0.CR1
    • Component/s: server
    • Labels:
      None
    • Environment:

      JBDS 5.0.1
      Fedora 17 32bit
      OpenJDK 1.6

    • Steps to Reproduce:
      Hide

      1. Set up a remote EAP6/AS7 server accessible over IPv6
      2. Set the server expose management port
      3. Make sure the launch config is set appropriately for IPv6 - you have a multicast address set up and prefer IPv6 addresses:
      -Djboss.default.multicast.address=ff01::1 -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true
      4. Set up and admin user on the remote runtime (bin/add-user.sh)
      5. Start the server and enter the login/passwd when prompted
      6. Check the workspace log - you will see the error - FAIL

      Show
      1. Set up a remote EAP6/AS7 server accessible over IPv6 2. Set the server expose management port 3. Make sure the launch config is set appropriately for IPv6 - you have a multicast address set up and prefer IPv6 addresses: -Djboss.default.multicast.address=ff01::1 -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true 4. Set up and admin user on the remote runtime (bin/add-user.sh) 5. Start the server and enter the login/passwd when prompted 6. Check the workspace log - you will see the error - FAIL

      Description

      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
      

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  rob.stryker Rob Stryker
                  Reporter:
                  mmalina Martin Malina
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: