Skip to main content

Glassfish v2 b19 webservice problem

9 replies [Last post]
vns1302vns
Offline
Joined: 2006-06-20

I deployed very simple webservice into glassfish v2 b19
When trying to test it from Admin Console that this what I get:

exception report

message

descriptionThe server encountered an internal error () that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: PWC1244: Servlet execution threw an exception

root cause

com.sun.xml.ws.util.ServiceConfigurationError: com.sun.tools.ws.api.wsdl.TWSDLExtensionHandler: Provider com.sun.tools.ws.addressing.jaxws.TWsaWSDLExtensionHandler not found

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
steveor
Offline
Joined: 2006-03-02

Hi

I was trying to re-stress test a web service that worked
under glassfish v1.

I get the same error on windows-xp sp2 using v2-b21

I tried the unix workaround translated to windows but ...

[#|2006-10-13T23:07:42.500+0100|INFO|sun-appserver-pe9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Application server startup complete.|#]

[#|2006-10-13T23:08:23.609+0100|SEVERE|sun-appserver-pe9.1|javax.enterprise.system.container.web|_ThreadID=11;_ThreadName=httpWorkerThread-8080-0;_RequestID=6aabe679-02bf-4736-b3b7-78203f8a2a12;|StandardWrapperValve[NotificationConsumerInterface]: PWC1406: Servlet.service() for servlet NotificationConsumerInterface threw exception
com.sun.xml.ws.util.ServiceConfigurationError: com.sun.tools.ws.api.wsdl.TWSDLExtensionHandler: Provider com.sun.tools.ws.addressing.jaxws.TWsaWSDLExtensionHandler not found
at com.sun.xml.ws.util.ServiceFinder.fail(ServiceFinder.java:227)
at com.sun.xml.ws.util.ServiceFinder.access$100(ServiceFinder.java:127)
at com.sun.xml.ws.util.ServiceFinder$LazyIterator.next(ServiceFinder.java:360)
at com.sun.xml.ws.util.ServiceFinder.toArray(ServiceFinder.java:211)
at com.sun.tools.ws.wsdl.parser.WSDLParser.(WSDLParser.java:110)
at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:143)
at com.sun.tools.ws.processor.config.ModelInfo.buildModel(ModelInfo.java:87)
at com.sun.tools.ws.processor.Processor.runModeler(Processor.java:81)
at com.sun.tools.ws.wscompile.CompileTool.run(CompileTool.java:566)
at com.sun.tools.ws.util.ToolBase.run(ToolBase.java:56)
at com.sun.tools.ws.util.WSToolsObjectFactoryImpl.wsimport(WSToolsObjectFactoryImpl.java:38)
at com.sun.enterprise.webservice.monitoring.WebServiceTesterServlet.wsImport(WebServiceTesterServlet.java:574)
at com.sun.enterprise.webservice.monitoring.WebServiceTesterServlet.initializePort(WebServiceTesterServlet.java:505)
at com.sun.enterprise.webservice.monitoring.WebServiceTesterServlet.doGet(WebServiceTesterServlet.java:166)
at com.sun.enterprise.webservice.monitoring.WebServiceTesterServlet.invoke(WebServiceTesterServlet.java:106)
at com.sun.enterprise.webservice.NewJAXWSServlet.doGet(NewJAXWSServlet.java:162)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:276)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:586)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:556)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:246)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:185)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:586)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:586)
at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:586)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:556)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:249)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:618)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.processNonBlocked(DefaultProcessorTask.java:549)
at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:790)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:328)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:251)
at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:205)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:103)
|#]

I'm also using netbeans v5.5 beta 2

Do I need to change my library settings in netbeans and recompile?

regards
Steve

fredferrao
Offline
Joined: 2006-10-06

ok, it worked now, thank you very much!!!
Hey, is this problem a bug? will it fixed?

vijaysr
Offline
Joined: 2003-06-11

This is a bug - there are 2 bugs pending on this. Mostly by GFv2-b22 only this will get fixed. Please let us know other problems if any - I will try to give you workarounds while we fix it. We are integating the WSZIT technologies into GFv2 right now and webserviec related features are not that stable as yet - apologies for the trouble.

fredferrao
Offline
Joined: 2006-10-06

I have same problem with GFv2 b20, but my problem occurs when I create a WebService Client from a WSDL URL.
What do you say about this vijaysr?

vijaysr
Offline
Joined: 2003-06-11

Even with the latest GFv2 builds, most of our dev tests are passing and all these dev tests (glassfish/appserv-tests/devtests/webservice/annotations/* and glassfish/appserv-tests/devtests/webservice/ejb_annotations/*) create client from a published WSDL. Given this, you have to give more info for me to help you

fredferrao
Offline
Joined: 2006-10-06

Well, I'm using:
GF v2 b20 with Netbeans 5.5 RC1

I created a new WebApplication and was creating a WebService, with some operations, then I needed create a WebService client from a WSDL URL in this application,
however the error occurs on creating client, this is the log of netbeans:

init:
wsimport-init:
Created dir: C:\Documents and Settings\Fred\WebApplication1\build\generated\wsimport\client
Created dir: C:\Documents and Settings\Fred\WebApplication1\build\generated\wsimport\binaries
wsimport-client-check-service1.asmx:
wsimport-client-service1.asmx:
Consider using /
so that wsimport won't do unnecessary compilation
com.sun.xml.ws.util.ServiceConfigurationError: com.sun.tools.ws.api.wsdl.TWSDLExtensionHandler: Provider com.sun.tools.ws.addressing.jaxws.TWsaWSDLExtensionHandler not found
BUILD FAILED (total time: 2 seconds)

In a JavaApplication that error don't occur. The WebService client is created with no error.

Thank you.

vijaysr
Offline
Joined: 2003-06-11

The workaround for this will be :

cd appserver_install/lib
cp webservices-tools.jar webservices-tools.jar.orig
mkdir t
cd t
jar xvf ../webservices-tools.jar
rm -rf META-INF/services/com.sun.tools.ws.api.TJavaGeneratorExtension
rm -rf META-INF/services/com.sun.tools.ws.api.wsdl.TWSDLExtensionHandler
jar cvf ../webservices-tools.jar *

Hope this helps

vijaysr
Offline
Joined: 2003-06-11

This is a known problem introduced with the introduction of WSIT technologies in GFv2. Please note that this affects the tester feature only and not if you write a real web service client. This will be fixed most probably in GFv2-b22 only. If this is too late, you might want to take GFv2-b15 or b16 - sorry for the trouble.

vns1302vns
Offline
Joined: 2006-06-20

[u]vijaysr[/u]

Thank you for answer and crarification.