[jbossws-issues] [JBoss JIRA] (JBWS-3563) Unable to connect to SOAP web service in IPv6 environment

Martin Malina (JIRA) jira-events at lists.jboss.org
Mon Oct 29 05:46:01 EDT 2012


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

Martin Malina edited comment on JBWS-3563 at 10/29/12 5:45 AM:
---------------------------------------------------------------

Alessio, we used this for the setup of the virtual machines: http://etherpad.corp.redhat.com/ipv6virtualboxsetup
So both virtual hosts have an interface which only has an IPv6 address assigned and no IPv4.
As for the EAP6 server, it was started from JBDS with these parameters:
Program arguments:
{code}
-mp "/home/jbossqa/runtimes/jboss-eap-6.0/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b fedoraa -bunsecure=fedoraa -Djboss.default.multicast.address=ff01::1 --server-config=standalone.xml
{code}
VM arguments:
{code}
-server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Dorg.jboss.resolver.warning=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=/home/jbossqa/runtimes/jboss-eap-6.0/standalone/log/boot.log" "-Dlogging.configuration=file:/home/jbossqa/runtimes/jboss-eap-6.0/standalone/configuration/logging.properties" "-Djboss.home.dir=/home/jbossqa/runtimes/jboss-eap-6.0"
{code}
If I look at the server process it looks like this:
{code}
 1760 pts/0    Sl     0:05              |       |       \_ /usr/java/jdk1.6.0_32/bin/java -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Dorg.jboss.resolver.warning=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=/home/jbossqa/runtimes/jboss-eap-6.0/standalone/log/boot.log -Dlogging.configuration=file:/home/jbossqa/runtimes/jboss-eap-6.0/standalone/configuration/logging.properties -Djboss.home.dir=/home/jbossqa/runtimes/jboss-eap-6.0 -Dfile.encoding=UTF-8 -classpath /home/jbossqa/runtimes/jboss-eap-6.0/jboss-modules.jar org.jboss.modules.Main -mp /home/jbossqa/runtimes/jboss-eap-6.0/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b fedoraa -bunsecure=fedoraa -Djboss.default.multicast.address=ff01::1 --server-config=standalone.xml
{code}
Is this what you wanted? Or do you still need some more information?
                
      was (Author: mmalina):
    Alesio, we used this for the setup of the virtual machines: http://etherpad.corp.redhat.com/ipv6virtualboxsetup
So both virtual hosts have an interface which only has an IPv6 address assigned and no IPv4.
As for the EAP6 server, it was started from JBDS with these parameters:
Program arguments:
{code}
-mp "/home/jbossqa/runtimes/jboss-eap-6.0/modules" -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b fedoraa -bunsecure=fedoraa -Djboss.default.multicast.address=ff01::1 --server-config=standalone.xml
{code}
VM arguments:
{code}
-server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Dorg.jboss.resolver.warning=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=/home/jbossqa/runtimes/jboss-eap-6.0/standalone/log/boot.log" "-Dlogging.configuration=file:/home/jbossqa/runtimes/jboss-eap-6.0/standalone/configuration/logging.properties" "-Djboss.home.dir=/home/jbossqa/runtimes/jboss-eap-6.0"
{code}
If I look at the server process it looks like this:
{code}
 1760 pts/0    Sl     0:05              |       |       \_ /usr/java/jdk1.6.0_32/bin/java -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Dorg.jboss.resolver.warning=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=/home/jbossqa/runtimes/jboss-eap-6.0/standalone/log/boot.log -Dlogging.configuration=file:/home/jbossqa/runtimes/jboss-eap-6.0/standalone/configuration/logging.properties -Djboss.home.dir=/home/jbossqa/runtimes/jboss-eap-6.0 -Dfile.encoding=UTF-8 -classpath /home/jbossqa/runtimes/jboss-eap-6.0/jboss-modules.jar org.jboss.modules.Main -mp /home/jbossqa/runtimes/jboss-eap-6.0/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b fedoraa -bunsecure=fedoraa -Djboss.default.multicast.address=ff01::1 --server-config=standalone.xml
{code}
Is this what you wanted? Or do you still need some more information?
                  
> Unable to connect to SOAP web service in IPv6 environment
> ---------------------------------------------------------
>
>                 Key: JBWS-3563
>                 URL: https://issues.jboss.org/browse/JBWS-3563
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: ws-addressing
>         Environment: Related JIRA was created for JBT 3.3.0 GA
>            Reporter: Jaroslav Jankovič
>            Assignee: Alessio Soldano
>
> See details here [JBIDE-12283|https://issues.jboss.org/browse/JBIDE-12283]

--
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 jbossws-issues mailing list