7:35 a.m.
Jaroslav Jankovič created JBWS-3563:
---------------------------------------
Summary: 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č
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
9:07 a.m.
[
https://issues.jboss.org/browse/JBWS-3563?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on JBWS-3563:
---------------------------------------
Jaroslav,
in order for us to have a look a this, can you please provide / tell us:
1) the ws endpoint archive you're deploying
2) how you're configuring IPv6
3) the client code or a capture of the soap message + http headers you're sending
We've been running IPv6 tests for EAP6, so this should definitely work.
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
9:25 a.m.
[
https://issues.jboss.org/browse/JBWS-3563?page=com.atlassian.jira.plugin....
]
Jaroslav Jankovič commented on JBWS-3563:
-----------------------------------------
Alexio, did you look into linked JBT JIRA? I believe there are all of (at least most of)
answers for your questions.
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
9:40 a.m.
[
https://issues.jboss.org/browse/JBWS-3563?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on JBWS-3563:
---------------------------------------
Hi Jaroslav,
yes, I've had a brief look at that and don't see answer to any of my 3 questions
above, sorry.
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
9:57 a.m.
[
https://issues.jboss.org/browse/JBWS-3563?page=com.atlassian.jira.plugin....
]
Jaroslav Jankovič commented on JBWS-3563:
-----------------------------------------
Ok then:
1) it was simple soap web service created with jbt wizard (Simple Web Service wizard)
2) there were made two instances of fedora virtualbox images which are connected to each
other with IPv6
3) I was testing it with WS Tester. But as I said in one comment: "Try in web
browser: http://fedoraa:8080/jbide-12283/HelloWorld?wsdl and press enter - in JBDS console
you will see the same error as I saw"
Hope, it'll help
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
10:19 a.m.
[
https://issues.jboss.org/browse/JBWS-3563?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on JBWS-3563:
---------------------------------------
Sorry, but it doesn't. The QE team has been running IPv6 testing for EAP6, using the
whole JBossWS testsuite. So "any simple ws endpoint" on "virtualbox images
connected with IPv6" is not enough. In order for reproducing your issue, we at least
need to know exactly *how* you're setting IPv6.
Consider having a look at [1] and [2] for info on how we setup IPv6, etc.
[1]
https://issues.jboss.org/browse/JBWS-3458?page=com.atlassian.jira.plugin....
[2] https://issues.jboss.org/browse/JBPAPP-8441
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
10:42 a.m.
[
https://issues.jboss.org/browse/JBWS-3563?page=com.atlassian.jira.plugin....
]
Martin Malina commented on JBWS-3563:
-------------------------------------
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
10:46 a.m.
[
https://issues.jboss.org/browse/JBWS-3563?page=com.atlassian.jira.plugin....
]
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
2:59 p.m.
[
https://issues.jboss.org/browse/JBWS-3563?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on JBWS-3563:
---------------------------------------
Thanks Martin. We'll download the images and try reproducing.
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
4201
days inactive
4201
days old
jbossws-issues@lists.jboss.org
8 comments
3 participants
participants (3)
-
Alessio Soldano (JIRA) -
Jaroslav Jankovič (JIRA)
-
Martin Malina (JIRA)