In 5.6, we came across the below exception while invoking a soap web service from our application:
com.sun.xml.internal.ws.client.ClientTransportException: The server sent HTTP status code 200: OK
at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.createResponsePacket(HttpTransportPipe.java:266)
at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:217)
at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:130)
at com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:124)
at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:1121)
at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:1035)
at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:1004)
at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:862)
at com.sun.xml.internal.ws.client.Stub.process(Stub.java:448)
at com.sun.xml.internal.ws.client.sei.SEIStub.doProcess(SEIStub.java:178)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:93)
at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:77)
at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:147)
at com.sun.proxy.$Proxy208.authenticatePortalUser(Unknown Source)
at auk.corp.customerportal.adapter.authenticateportaluser.AuthenticatePortalUserAdapter.invokeWebService(AuthenticatePortalUserAdapter.java:146)
at auk.corp.customerportal.adapter.authenticateportaluser.AuthenticatePortalUserAdapter.invokeWebService(AuthenticatePortalUserAdapter.java:55)
at auk.corp.cssportal.domain.login.services.impl.AuthenticatePortalUserServiceImpl.authenticatePortalUser(AuthenticatePortalUserServiceImpl.java:67)
at auk.corp.cssportal.command.login.servlets.AuthenticatePortalUserCommand.doPost(AuthenticatePortalUserCommand.java:229)
at org.apache.sling.api.servlets.SlingAllMethodsServlet.mayService(SlingAllMethodsServlet.java:149)....
This issue is resolved by adding the below jars in the lib/endorsed folder of the jboss server:
xercesImpl.jar
xalan.jar
stax-api.jar
serializer.jar
resolver.jar
jaxb-api.jar
activation.jar
jbossws-native-saaj.jar
jbossws-native-jaxws.jar
jbossws-native-jaxws-ext.jar
After migrating the code to 6.2, we are facing the same issue again.
Is there any alternative jars to be added in the Jetty server that can resolve the issue? If so, how do we include them in the application.
Please help!!
