Description of problem: We can see intermittent failures of different tests with the following common symptoms: Test is reading wsdl from server, failure cause is Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:8080/anyname?wsdl In server log we see following exception ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/jaxrpc-samples-jsr109pojo-doc].[TestService]] (http-/127.0.0.1:8080-23) JBWEB000235: Allocate exception for servlet TestService: java.lang.NullPointerException at org.jboss.wsf.stack.jbws.WebAppResolver.query(WebAppResolver.java:58) at org.jboss.as.webservices.util.ServiceContainerEndpointRegistry.resolve(ServiceContainerEndpointRegistry.java:68) at org.jboss.wsf.stack.jbws.AbstractEndpointServlet.initEndpoint(AbstractEndpointServlet.java:149) at org.jboss.wsf.stack.jbws.AbstractEndpointServlet.initServiceEndpoint(AbstractEndpointServlet.java:126) at org.jboss.wsf.stack.jbws.AbstractEndpointServlet.init(AbstractEndpointServlet.java:74) at org.jboss.wsf.spi.deployment.WSFServlet.init(WSFServlet.java:57) [jbossws-spi-2.2.1.Final-redhat-1.jar:2.2.1.Final-redhat-1] at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:950) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:151) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.3.0.Final-redhat-8.jar:7.3.0.Final-redhat-8] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] Version-Release number of selected component (if applicable): EAP 6.2.0.ER1-5 How reproducible: intermittent Additional info: I would suspect thread safe related issues in class org.jboss.wsf.stack.jbws.WebAppResolver I think fails test using deployment done after the exception is thrown
Upstream jira: https://issues.jboss.org/browse/JBWS-3717
As per Petr analysis, the actual reason for the problem here should be https://issues.jboss.org/browse/JBWS-3719 JBWS-3717 could also cause the same effect, but is most likely not the first culprit here.
https://github.com/jbossas/jboss-eap/pull/576
Alessio Soldano <asoldano> updated the status of jira JBWS-3719 to Closed
Alessio Soldano <asoldano> updated the status of jira JBWS-3717 to Closed
verified - I've check test failures with symptoms described are not present on EAP 6.2.0.ER7
I can see from comments in this and attached JIRAs that the server error was being caused by incorrect endpoints being returned. But I'm not able to ascertain how this was corrected. With EAP 6.2 GA looming, I'm requesting a draft release note text (including layman's description of the problem and the fix) be supplied in the Doc Text field above. Any and all help is appreciated, Alessio.
Scott, honestly I believe we don't need any release note here. This issue was a consequence of changes that were applied in a early 6.2 ER, so not something the customer can have experimented at all.
Thanks for the update Alessio. I've marked this for exclusion from the release notes.