2 Replies Latest reply on Oct 25, 2012 3:51 AM by asoldano

    Parallel invocations of JAX WS services

    nishant_hadole
    nishant_hadole Apr 17, 2012 3:23 AM

      We are facing issue for our production setup. The details are as follows:

       

      1.       JBoss SOA Platform: Embedded Server - Version 5.1.0.GA

      2.       Scenario - Parallel invocations of JAX WS services

      3.       Exception - javax.xml.ws.WebServiceException: java.lang.ClassCastException

      4.       Native versions – bundled with AS, jbossws-native-3.1.2.SP7

       

       

      Reference:

       

      https://community.jboss.org/thread/148073?start=0&tstart=0

       

      https://issues.jboss.org/browse/JBWS-2934

       

       

      I tried installing jbossws-native-3.4.1.GA onto my server and deployment completed successfully. But the server refuses to start with following error:

       

      java.lang.SecurityException: class "org.jboss.metadata.MetaData"'s signer information does not match signer information of other classes in the same package

       

       

      Kindly suggest how to proceed with the fix.

       

       

      Regards,

      Nishant

        • 1. Re: Parallel invocations of JAX WS services
          cacao
          cacao Oct 24, 2012 1:19 PM (in response to nishant_hadole)

          Hi Nishant,

           

          Did you find any solution to the above problem ? I am getting a similar exception while starting the server, with Jbossws-cxf. (i am using jboss eap 5.1.0 and trying to install jbossws-cxf 3.4.0 GA.

           

          Thanks!

            • Actions
          • 2. Re: Parallel invocations of JAX WS services
            asoldano
            asoldano Oct 25, 2012 3:51 AM (in response to cacao)

            Folks,

            if you're a customer of a JBoss Platform product (JBoss Enterprise Application Platform EAP or JBoss SOA Platform) please got through your subscription channel / support contact and you'll get the proper update or patch for you. You're not supposed to manually change the productized JBossWS version in there and other community versions are likely not going to work. The bug mentioned here has been fixed in EAP 5.1.1 anyway.

              • Actions