[jbosstools-issues] [JBoss JIRA] (JBIDE-12352) Remote management connection to servers cannot be established with IPv6

[Snjezana Peco (JIRA)]

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

Snjezana Peco commented on JBIDE-12352:
---------------------------------------

A remote server over IPV6 can be set as follows:

- configure a remote RSE server (I have tried a SSH-Only server)
- set Host name to ip6-localhost (::1)
- set Behavior Profile to Remote 
- check "Listen on all interfaces to allow remote web connections" and "Expose your management port as the server's hostname"
- add "-Djava.util.logging.manager=org.jboss.logmanager.LogManager" to the launch configuration

The launch configuration should contain the following options:

Start command:

{code}
java "-Dprogram.name=JBossTools: jboss-eap" -server -Xms1024m -Xmx1024m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true "-Dorg.jboss.boot.log.file=<SERVER_HOME>/standalone/log/boot.log" "-Dlogging.configuration=file:<SERVER_HOME>/standalone/configuration/logging.properties" "-Djboss.home.dir=<SERVER_HOME>" -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=ip6-localhost -jar <SERVER_HOME>/jboss-modules.jar  -mp "<SERVER_HOME>/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b ip6-localhost --server-config=standalone.xml -Djava.util.logging.manager=org.jboss.logmanager.LogManager&
{code}

Stop command:

{code}
<SERVER_HOME>/bin/jboss-cli.sh --controller=IP6-LOCALHOST:9999 --connect command=:shutdown
{code}

Sometimes it is necessary to start the server twice because it can't load the org.jboss.logmanager.LogManager class.
I think, the solution is to add jboss-logmanager-XXX.jar to bootclasspath (-Xbootclasspath/p:<path_to_jboss-logmanager.jar>)  

The -Djboss.default.multicast.address=ff01::1 argument is related to clustering.

> Remote management connection to servers cannot be established with IPv6
> -----------------------------------------------------------------------
>
>                 Key: JBIDE-12352
>                 URL: https://issues.jboss.org/browse/JBIDE-12352
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.3.1.Final
>         Environment: JBDS 5.0.1
> Fedora 17 32bit
> OpenJDK 1.6
>            Reporter: Martin Malina
>            Priority: Critical
>             Fix For: 4.2.x, 4.3.0.Alpha1
>
>
> 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:
> {code}
> 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
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)