With upgrade to JBossWS 4.3.2.Final-redhat-1 in 6.4.0.DR10 isssues occured on IBM JDK6. Running JBossWS TS most of the tests failed (~410 out of ~670). There are no unexpected problems with other JDKs (even IBM7 is fine), no such problems with older EAP builds. I managed to reproduce the same issues locally (using JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr16-20140416_196573 (JIT enabled, AOT enabled)), will do some more investigation. How reproducible: always Steps to Reproduce: use IBM JDK6 for running server and testsuite Actual results: most of the failures seems to end up with the same error message (Instead of SOAP message, server answers with HTML stating HTTP 500 status): Error Message Response was of unexpected text/html ContentType. Incoming portion of HTML stream: <html><head><title>JBoss Web/7.5.0.Beta4 - JBWEB000064: Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>JBWEB000065: HTTP Status 500 - JBWEB000248: Servlet execution threw an exception</h1><HR size="1" noshade="noshade"><p><b>JBWEB000309: type</b> JBWEB000066: Exception report</p><p><b>JBWEB000068: message</b> <u>JBWEB000248: Servlet execution threw an exception</u></p><p><b>JBWEB000069: description</b> <u>JBWEB000145: The server encountered an internal error that prevented it from fulfilling this request.</u></p><p><b>JBWEB000070: exception</b> <pre>javax.servlet.ServletException: JBWEB000248: Servlet execution threw an exception </pre></p><p><b>JBWEB000071: root cause</b> <pre>java.lang.NoClassDefFoundError: org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor$HeadersProcessor (initialization failure) java.lang.J9VMInternals.initialize(J9VMInternals.java:141) org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:185) org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:65) org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272) org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:241) org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:97) org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:131) org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:88) org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286) org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206) javax.servlet.http.HttpServlet.service(HttpServlet.java:754) org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:136) org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) </pre></p><p><b>JBWEB000071: root cause</b> <pre>java.lang.NoSuchMethodError: javax/xml/stream/XMLEventFactory.newFactory()Ljavax/xml/stream/XMLEventFactory; org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor$HeadersProcessor.<clinit>(ReadHeadersInterceptor.java:275) java.lang.J9VMInternals.initializeImpl(Native Method) java.lang.J9VMInternals.initialize(J9VMInternals.java:201) org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:185) org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:65) org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272) org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:241) org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:97) org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:131) org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:88) org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286) org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206) javax.servlet.http.HttpServlet.service(HttpServlet.java:754) org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:136) org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) javax.servlet.http.HttpServlet.service(HttpServlet.java:847) </pre></p><p><b>JBWEB000072: note</b> <u>JBWEB000073: The full stack trace of the root cause is available in the JBoss Web/7.5.0.Beta4 logs.</u></p><HR size="1" noshade="noshade"><h3>JBoss Web/7.5.0.Beta4</h3></body></html> Expected results: no such failures Additional info: jobs with failures https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-6x-jbossws-testsuite-rhel/54/ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-6x-jbossws-testsuite-rhel-ppc64/14/ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-6x-jbossws-testsuite-rhel-ipv6-pure/53/ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-WS/job/eap-6x-jbossws-testsuite-rhel-ipv6-dualstack/40/
Judging from the stacktrace, this looks to be the issue here: https://issues.apache.org/jira/browse/CXF-6068
I tried to prepare modified cxf-rt-bindings-soap-2.7.13.redhat-4.jar with the fix from CXF-6068 and used it for test execution (in EAP modules and maven repo) - issues on IBM JDK6 are gone.
Just for note: Also AS Testsuite gives ~100 new failures on IBM6 with DR10. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-as-testsuite-rhel/30/RELEASE=6.4.0,jdk=ibm1.6,label_exp=eap-sustaining%20&&%20RHEL5%20&&%20x86_64/testReport/
Same issue occurs in PicketLink 2.1.x and 2.5.x Testsuite with IBM6: e.g.: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Security-group/view/EAP-6.4.x-DR-security/job/eap-64-picketlink-testsuite-25x-rhel/jdk=ibm1.6,label_exp=RHEL6&&x86_64/20/ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Security-group/view/EAP-6.4.x-DR-security/job/eap-64-picketlink-testsuite-21x-rhel/jdk=ibm16,label_exp=RHEL6&&x86_64/13/
Verified on 6.4.0.ER1