5 Replies Latest reply: Jul 20, 2010 3:29 AM by Rizwan P RSS

    Jboss 4.2.3 IllegalArgumentException for Invoking webservice in JDK1.6

    Rizwan P Newbie

      Hi,

       

      I am getting strange error on different jboss instances while invoking the webservice.

       

      The configuration for both the server instance is same no change just a duplicate copy of other.

       

      Below is the error I am receiving while invoking the webservice call at first time, and after that the working of client is halt.

       

       

      java.lang.ExceptionInInitializerError
                at sun.reflect.NativeConstructorAccessorImple.newInstance0(Native Method)
                ....
                at javax.xml.soap.FactoryFinder.newInstance(FactoryFinder.java:55)
                ....
                at javax.xml.soap.MessageFactory.newInstance(MessageFactory.java:144)
                at com.sun.xml.ws.api.SOAPVersion.<init>(SOAPVersion.java:178)
                ....
      Caused by: java.lang.IllegalArgumentException: com.sun.xml.internal.messaging.saaj.soap.LocalStrings != com.sun.xml.messaging.saaj.soap.LocalStrings
                at java.util.logging.Logger.getLogger(Logger.java:314)
                at com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImple.<init>(SAAJMetaFactoryImpl.java:52)
      
      

       

      Please provide suggestion how to resolve this problem.

       

      saaj-impl.jar version : 1.3 (Present at the server's jbossws.sar directory and nowhere on the instance)

      JDK : 1.6.013

      Jboss : 4.2.3

      Jboss Metro : 3.1.1.GA

        • 1. Re: Jboss 4.2.3 IllegalArgumentException for Invoking webservice in JDK1.6
          Rizwan P Newbie

          The issues seems to be the class loading one. But I am not getting the exact root cause to occur this , still the problem is not resolved.

           

          Is anyone assist,please.

           

          Sending the more stack trace for the reference :

           

          java.lang.ExceptionInInitializerError

          2010-07-14 14:04:51,914 ERROR [STDERR]  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
          2010-07-14 14:04:51,914 ERROR [STDERR]  at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
          2010-07-14 14:04:51,914 ERROR [STDERR]  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
          2010-07-14 14:04:51,914 ERROR [STDERR]  at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
          2010-07-14 14:04:51,914 ERROR [STDERR]  at java.lang.Class.newInstance0(Class.java:355)
          2010-07-14 14:04:51,914 ERROR [STDERR]  at java.lang.Class.newInstance(Class.java:308)
          2010-07-14 14:04:51,914 ERROR [STDERR]  at javax.xml.soap.FactoryFinder.newInstance(FactoryFinder.java:55)
          2010-07-14 14:04:51,914 ERROR [STDERR]  at javax.xml.soap.FactoryFinder.find(FactoryFinder.java:182)
          2010-07-14 14:04:51,914 ERROR [STDERR]  at javax.xml.soap.SAAJMetaFactory.getInstance(SAAJMetaFactory.java:75)
          2010-07-14 14:04:51,914 ERROR [STDERR]  at javax.xml.soap.MessageFactory.newInstance(MessageFactory.java:144)
          2010-07-14 14:04:51,914 ERROR [STDERR]  at com.sun.xml.internal.ws.api.SOAPVersion.<init>(SOAPVersion.java:163)
          2010-07-14 14:04:51,914 ERROR [STDERR]  at com.sun.xml.internal.ws.api.SOAPVersion.<clinit>(SOAPVersion.java:68)
          2010-07-14 14:04:51,914 ERROR [STDERR]  at com.sun.xml.internal.ws.api.BindingID.<clinit>(BindingID.java:304)
          2010-07-14 14:04:51,915 ERROR [STDERR]  at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parseBinding(RuntimeWSDLParser.java:398)
          2010-07-14 14:04:51,915 ERROR [STDERR]  at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parseWSDL(RuntimeWSDLParser.java:295)
          2010-07-14 14:04:51,915 ERROR [STDERR]  at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:124)
          2010-07-14 14:04:51,915 ERROR [STDERR]  at com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:226)
          2010-07-14 14:04:51,915 ERROR [STDERR]  at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:189)
          2010-07-14 14:04:51,915 ERROR [STDERR]  at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:159)
          2010-07-14 14:04:51,915 ERROR [STDERR]  at com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:83)
          2010-07-14 14:04:51,915 ERROR [STDERR]  at javax.xml.ws.Service.<init>(Service.java:56)
          ......

          2010-07-14 14:04:51,915 ERROR [STDERR] Caused by: java.lang.IllegalArgumentException: com.sun.xml.messaging.saaj.soap.LocalStrings != com.sun.xml.internal.me
          ssaging.saaj.soap.LocalStrings
          2010-07-14 14:04:51,915 ERROR [STDERR]  at java.util.logging.Logger.getLogger(Logger.java:314)
          2010-07-14 14:04:51,915 ERROR [STDERR]  at com.sun.xml.internal.messaging.saaj.soap.SAAJMetaFactoryImpl.<clinit>(SAAJMetaFactoryImpl.java:35)
          2010-07-14 14:04:51,915 ERROR [STDERR]  ... 30 more
          .....

          2010-07-14 14:04:51,972 ERROR [STDERR] java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.internal.ws.api.BindingID
          2010-07-14 14:04:51,972 ERROR [STDERR]  at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parseBinding(RuntimeWSDLParser.java:398)
          2010-07-14 14:04:51,972 ERROR [STDERR]  at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parseWSDL(RuntimeWSDLParser.java:295)
          2010-07-14 14:04:51,972 ERROR [STDERR]  at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:124)
          2010-07-14 14:04:51,972 ERROR [STDERR]  at com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:226)
          2010-07-14 14:04:51,972 ERROR [STDERR]  at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:189)
          2010-07-14 14:04:51,972 ERROR [STDERR]  at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:159)
          2010-07-14 14:04:51,972 ERROR [STDERR]  at com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:83)
          2010-07-14 14:04:51,973 ERROR [STDERR]  at javax.xml.ws.Service.<init>(Service.java:56)

          • 2. Re: Jboss 4.2.3 IllegalArgumentException for Invoking webservice in JDK1.6
            Jim Ma Apprentice

            Did you try jdk 1.5 ? Is there same error when start  jboss with JDK1.5 ?

            • 3. Re: Jboss 4.2.3 IllegalArgumentException for Invoking webservice in JDK1.6
              Rizwan P Newbie

              Hi Jim,

               

              Thanks for responding.

               

              No, i have not checked with the JDK1.5 with Jboss.

               

              Giving more details about the problem occurrence :

               

              There are two webservices client present bundled in different applications but deployed on the same jboss instance.

               

              When any of them initializes first, then that client works smoothly without this error.

               

              But, the second client always give this error.

               

              Hope this might give some helpful info about the error.

              • 4. Re: Jboss 4.2.3 IllegalArgumentException for Invoking webservice in JDK1.6
                Daniel Cullender Newbie

                are these applications packaged in ear's? if so, change the ear-deployer.xml in the deploy directory to use isolated classloaders.

                • 5. Re: Jboss 4.2.3 IllegalArgumentException for Invoking webservice in JDK1.6
                  Rizwan P Newbie

                  Hi Daniel,

                   

                  These two webservice clients are not being packed in ear. These are two different web applications packaged in different wars.

                   

                  I am suspicious that, this is being purely a class-loading issue occurring because of initialization of one of the client halting the work of other.

                   

                  Now I have bundled all supporting jars together in both the web application specially webservice-rt.jar. I am monitoring this problem, not it was occurring very rarely. but still the problem is not resolved.

                   

                  Can you please assist where to look.