[JBossWS] - Re: NPE deploying web services in service archive in CR1 rel
by adinn
I managed to debug this a little further and have identified why the startup code is hanging -- it is because of something my code is doing (I'll come to that in a second). I still don't know why the WebService port is being looked up before it is defined so there is still an issue there.
The hang is because I am trying to coordinate initialization of my war apps and the XTS service which deploys them. The problem I face is that the listeners are run in an arbitrary order but the war apps have initialization dependencies. So, I make the war listeners register callbacks in a fixed sequence. If any of them finds that the sequence is complete after regsitering then it runs all the callbacks.
This was ok until I added transaction recovery which requires initialization in the XTS service start() routine before the wars can be initialized. I had assumed that the XTS service start() call happened in parallel with the war listener calls so I added a latch in the callback runner which was released by the XTS service start(). If the runner gets there first it does a wait() and the start() call wakes it with a notfiy(). It appears that the start() and listener call actually run in the same thread in arbitrary order and up until now the start() call has always run first. Now, the sar start() call occasionally gets run last, resulting in a deadlock. I guess I need to make my war apps depend on the XTS service bean.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184411#4184411
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184411
15 years, 6 months
[JBossWS] - Re: NPE deploying web services in service archive in CR1 rel
by adinn
I had a little further look into this and found that the errors occur as follows:
During deployment of the endpoints declared in my wars a call is made to AbstractServerConfig.getConnectorPort(). This fetches the WS Server MBean and tries to lookup objects of type "jboss.web:type=Connector,*". At the point where the lookup fails the jboss.web MBean has only one entry for the WebServer.
In the run that I managed to debug the type=Connector entries were added at a later point. So, some of the subsequent calls to getConnectorPort() succeeded and also the AS bootstrap did not hang. I was unable to debug a case where the bootstrap did hang.
So, although this is a lot better than 3.0.3 it looks like there is still a race where the deployers may try to start the endpoints before everything they need is in place.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184266#4184266
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184266
15 years, 6 months
[JBossWS] - ERROR without exception: JAX-WS context listener initializin
by QPool.Char
Hello dear forum,
i follow the detailed descriptions to make a simple WebService with JDK 6 and JBoss 4.2.3 from this website: http://blog.vinodsingh.com/2008/09/jax-ws-web-service-and-jboss.html?show...
When i deploy the .war to JBoss, i get the following Errors:
| 17:07:14,312 INFO [TomcatDeployer] deploy, ctxPath=/HelloWorld, warUrl=.../tmp/deploy/tmp7738HelloWorld-exp.war/
| 17:07:14,781 ERROR [STDERR] 23.10.2008 17:07:14 com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
| INFO: WSSERVLET12: JAX-WS context listener initializing
| 17:07:16,109 ERROR [STDERR] 23.10.2008 17:07:16 com.sun.xml.ws.transport.http.servlet.WSServletDelegate <init>
| INFO: WSSERVLET14: JAX-WS servlet initializing
| 17:07:17,000 INFO [WSDLFilePublisher] WSDL published to: file:/C:/JavaStuff/jboss-4.2.3.GA/server/default/data/wsdl/HelloWorld.war/HelloWorldService7739.wsdl
Generating some client stubs worked, but trying to invoke a client, i get the following exception:
| 17:14:38,093 ERROR [[HelloWorldWebService]] Servlet.service() for servlet HelloWorldWebService threw exception
| java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl cannot be cast to org.jboss.ws.core.soap.SOAPMessageImpl
| at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:245)
I have also tried JBoss 5.0 and the JBossWS-patches to jbossws 3.0.4.
I believe that there are some class-loading problems with Java 6, and filled the ${JBOSS_HOME}/lib/endorsed directory with jars mentioned on this page: http://thesmallpotato.blogspot.com/2007/06/jdk-16-jboss-420-ejb3-web-serv... ,but it did not help. I then added jboss-jaxws.jar and jboss-jaxws-ext.jar, but without success again...
So i thought maybe the error comes from my web.xml, which i have a question for:
| <servlet>
| <servlet-name>HelloWorldWebService</servlet-name>
| <servlet-class>com.sun.xml.ws.transport.http.servlet.WSServlet</servlet-class>
| <!-- servlet-class>biz.accelsis.helloworld.HelloWorldWS</servlet-class> -->
| </servlet>
|
Can you tell me which value to put into the <servlet-class> tag?
Thx in advance for all the help, i am really stucked here.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184257#4184257
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184257
15 years, 6 months