Help Desk Ticket Reference: https://na7.salesforce.com/500A000000Au90w project_key: JBPAPP6 It tries to create this class if CXF is packaged in the war: org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation And this stack is logged as a warning: 11:08:40,879 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register module: Module "deployment.test.war:main" from Service Module Loader 11:08:40,905 WARN [org.jboss.as.ee] (MSC service thread 1-6) JBAS011006: Not installing optional component org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:83) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] If Metro is packaged in the war, it tries to load com.sun.xml.ws.transport.http.servlet.WSAsyncListener and logs a warning with this stack: 16:48:57,302 WARN [org.jboss.as.ee] (MSC service thread 1-1) JBAS011006: Not installing optional component com.sun.xml.ws.transport.http.servlet.WSAsyncListener$1 due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class com.sun.xml.ws.transport.http.servlet.WSAsyncListener$1 at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:83) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
Link: Added: This issue Cloned from AS7-5178
Workflow: Removed: GIT Pull Request workflow Added: jira Security: Added: Public Docs QE Status: Added: NEW
Link: Added: This issue incorporates AS7-5178
Ok, so this is about the EE subsystem, not the web subsystem. But the async listeners are really components [they can be injected, obviously], so there's probably nothing wrong here.
I didn't see an EE so I'm marking Other. David and I had been discussing this a week ago and he seemed to think it was a bug.
Help Desk Ticket Reference: Added: https://na7.salesforce.com/500A000000Au90w
Bugzilla Update: Added: Perform
Bugzilla References: Added: https://bugzilla.redhat.com/show_bug.cgi?id=852679
Docs QE Status: Removed: NEW
RH Bugzilla Integration <no-reply> updated the status of jira JBPAPP6-1399 to Closed
Hi. I there plan to include fix for this item in EAP 610 ? If yes, jboss-eap-6.1.0 flag must be selected to enter 3-ACK process. Please set pm, dev, qa acks to '?' too.
The same WARN level log and stack trace happens with org.springframework.web.context.request.async.StandardServletAsyncWebRequest. Both of Servlet3Continuation and StandardServletAsyncWebRequest implement javax.servlet.AsyncListener and all instances of the interface are expected to have the default constructor by the current implementation (due to https://issues.jboss.org/browse/JBWEB-224). But I think it's a strong assumption. Spec says some of AsyncListener instance must have a zero argument constructor [1], but I guess not all instances must. Shouldn't we expect the default constructor only for annotated ones like @ManagedBean? [1] http://docs.oracle.com/javaee/6/api/javax/servlet/AsyncContext.html#createListener%28java.lang.Class%29
As discussion done in WFLY-924 [1], the stacktrace was moved into DEBUG level in the upstream. Make sure we'll have it in the next release of EAP. [1] https://issues.jboss.org/browse/WFLY-924 a.k.a. AS7-5178
Backport the upstream fix into jboss-eap/6.x. https://github.com/jbossas/jboss-eap/pull/390
Verified in EAP 6.2.0.ER4.