[jbosstools-issues] [JBoss JIRA] (JBIDE-12283) Unable to connect to SOAP web service in IPv6 environment
Brian Fitzpatrick (JIRA)
jira-events at lists.jboss.org
Mon Jul 16 12:21:06 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-12283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706141#comment-12706141 ]
Brian Fitzpatrick commented on JBIDE-12283:
-------------------------------------------
Through some luck and a different tool I have the virtual environment working now. Hooray!
That said, I'm getting a slightly different result than you're seeing, so I want to make sure I am reproducing the project you're deploying the same way you are. It's not working, but I'm seeing an "javax.xml.ws.WebServiceException: Unsupported endpoint address:" show up in the response body rather than the error you're seeing.
Here's my exception:
!ENTRY org.jboss.tools.ws.ui 4 0 2012-07-16 18:14:32.757
!MESSAGE No message
!STACK 0
java.lang.Exception: javax.xml.ws.WebServiceException: Unsupported endpoint address:
at org.jboss.tools.ws.ui.utils.JAXWSTester2.doTest(JAXWSTester2.java:205)
at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1803)
at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$34(JAXRSWSTestView2.java:1789)
at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$21.run(JAXRSWSTestView2.java:1706)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: javax.xml.ws.WebServiceException: Unsupported endpoint address:
at com.sun.xml.internal.ws.api.pipe.TransportTubeFactory.create(TransportTubeFactory.java:133)
at com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:101)
at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:587)
at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:546)
at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:531)
at com.sun.xml.internal.ws.api.pipe.Fiber.run(Fiber.java:380)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
That said... My steps are:
1) Create dynamic web project
2) Use the "Simple Web Service" New wizard to create a sample JAX-WS project.
3) Deploy it
4) Test using this wsdl: file:/home/jbossqa/runtimes/jboss-eap-6.0/standalone/data/wsdl/jbide-12283.war/HelloWorldService.wsdl
> Unable to connect to SOAP web service in IPv6 environment
> ---------------------------------------------------------
>
> Key: JBIDE-12283
> URL: https://issues.jboss.org/browse/JBIDE-12283
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Webservices
> Affects Versions: 3.3.0.Final
> Environment: Two Fedora 17 machines connected to each other with IPv6 protocol, JBDS 5.0.0 GA, EAP 6
> Reporter: Jaroslav Jankovič
> Assignee: Brian Fitzpatrick
> Priority: Blocker
> Fix For: 3.4.0.M1
>
>
> When I was trying to obtain the content of WSDL file of deployed SOAP WS, an error was thrown in error log and no content could be viewed:
> {code}
> 08:45:31,450 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/prj].[HelloWorld]] (http-/fc00:0:0:0:0:0:0:1%2:8080-1) Servlet.service() for servlet HelloWorld threw exception: javax.servlet.ServletException: Cannot obtain destination for: /prj/HelloWorld
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination(RequestHandlerImpl.java:164)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:81)
> at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:169)
> at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:185)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:113)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-1.jar:1.0.1.Final-redhat-1]
> at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
> at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi-2.0.3.GA-redhat-1.jar:2.0.3.GA-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-1.jar:1.0.1.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_32]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list