Why does WS failed when invoking through SOAP Client?

[smartgridder]

Hey to all!

Im stuck on this one:

I have a web service deployed to JBoss 5.1 with JBoss ESB 4.9. Now i want to invoke this web service by a SOAP Client. but this always failes and causes the following exception:

{code}
12:07:16,835 ERROR [[MyWebServiceSample_MyWebService]] Servlet.service() for servlet MyWebServiceSample_MyWebService threw exception
java.lang.NoClassDefFoundError: org/jboss/util/id/SerialVersion
          at javax.xml.soap.SOAPException.<clinit>(SOAPException.java:22)
          at javax.xml.soap.SOAPFactory.newInstance(SOAPFactory.java:48)
          at org.jboss.ws.core.soap.SOAPFactoryImpl.createElement(SOAPFactoryImpl.java:121)
          at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:136)
          at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:96)
          at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:294)
          at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:193)
          at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:455)
          at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
          at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
          at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
          at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
          at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
          at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
          at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
          at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
          at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
          at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
          at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
          at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
          at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
          at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
          at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
          at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
          at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
          at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
          at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
          at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
          at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
          at java.lang.Thread.run(Unknown Source)
{code}

It seams, that the SOAP Client works fine but something is wrong within the JBoss AS. I have checked if the class

{code} org/jboss/util/id/SerialVersion {code}

is known to the Jboss AS and...it obviously is! in the jboss-common-core.jar.

The same happens when i try out the security_cert sample from JBossESB quickstarts.

What is wrong? i searched the web but couldnt find any helpful posts.

Thanx in advance for your replies!

Max

[tcunning]

It sounds like org.jboss.util.id.SerialVersion is failing in its static block for some reason then.

From org.jboss.util.id.SerialVersion:

static
  {
    AccessController.doPrivileged(new PrivilegedAction()
    {
      public Object run()
      {
        try
        {
          if (System.getProperty("org.jboss.j2ee.LegacySerialization") != null)
            SerialVersion.version = 0;
        }
        catch (Throwable ignored)
        {
        }
        return null;
      }
    });
  }

Any ideas why this might fail on your system?     Maybe attach a debugger and see which line it is failing on?

[smartgridder]

Hey Tom!

Tahnk you very much for your reply. I have no clue why this fails on my system. Im relatively new to JBoss so could you please tell me how to attatch a debugger?

Thanx

Max

[tcunning]

Here's a decent article which explains the steps through Eclipse (not sure what IDE you are using - if you are using NetBeans or Idea, I think there's similar documentation out there).

http://luckylarry.co.uk/programming-tutorials/jboss/how-to-setup-debugging-in-eclipse-for-jboss/

[smartgridder]

Thank you very much Tom!

I solved the problem by reinstalling JBoss 5.1.0 AS and deployed JBoss ESB 4.11 to it.

The wiered thing is, that if you then try to create an ESB-Project in JBoss Developer Studio for JBoss ESB 4.11 configured (marked yellow):

you cannot deploy this to the JBoss AS Server. It always says:

so i configured new JBoss ESB Projects for JBoss ESB 4.10 and that finally worked out. But this workaround is kind of ugly isn't it?

Oh! I almost forgot! the steps above worked to get the Project deployed but you also have to add the following JARs to JBOSS_HOME/lib/endorsed to work around the SOAPException you will get...well i got it ;-)

jbossws-native-jaxrpc.jar

jbossws-native-jaxws.jar

jbossws-native-jaxws-ext.jar

jbossws-native-saaj.jar

And then: it worked! awesome :-D

[tcunning]

Glad you got everything sorted out!     The ESB 4.11 deployment issue is a known issue -

https://issues.jboss.org/browse/jbds-2394

As you said, for now you can work around it by just choosing ESB 4.10.