Spring 3.2.x (StandardServletAsyncWebRequest) with jboss 7.1.3

[ks-appendium]

Hi,

I am trying to upgrade from Spring 3.1.4 to Spring 3.2.3 - after I have replaced the jars, the application does not start and get the following error message

14:19:01,692 WARN  [org.jboss.as.ee] (MSC service thread 1-4) JBAS011006: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.springframework.web.context.request.async.StandardServletAsyncWebRequest
          at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:607)
          at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:83)
          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.3.Final.jar:7.1.3.Final]
          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
          at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]

I have read on multiple discussions that I should just ignore the warning but further down - I get the following

JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.deployment.subunit."xxxx-ear.ear"."xxxx-web.war".component."org.springframework.web.context.request.async.StandardServletAsyncWebRequest".START (missing) dependents: [service jboss.deployment.subunit."xxxx-ear.ear"."xxxx-ejb.jar".INSTALL] 
      service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.xxxxStartup (missing) dependents: [service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.xxxxStartup.ValidatorFactory, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.xxxxStartup.HandleDelegate, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.xxxxStartup.ORB, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.xxxxStartup.Validator] 
      service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.AuditMonitoringForPersistenceMDB (missing) dependents: [service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.AuditMonitoringForPersistenceMDB.Validator, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.AuditMonitoringForPersistenceMDB.HandleDelegate, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.AuditMonitoringForPersistenceMDB.ORB, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.AuditMonitoringForPersistenceMDB.ValidatorFactory] 
      service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinessEventClientRouterMDB (missing) dependents: [service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinessEventClientRouterMDB.ORB, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinessEventClientRouterMDB.ValidatorFactory, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinessEventClientRouterMDB.HandleDelegate, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinessEventClientRouterMDB.Validator] 
      service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinessEventMonitoringForProceedingStageablesMDB (missing) dependents: [service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinessEventMonitoringForProceedingStageablesMDB.Validator, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinessEventMonitoringForProceedingStageablesMDB.HandleDelegate, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinessEventMonitoringForProceedingStageablesMDB.ValidatorFactory, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinessEventMonitoringForProceedingStageablesMDB.ORB] 
      service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinessEventMonitoringMDB (missing) dependents: [service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinessEventMonitoringMDB.HandleDelegate, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinessEventMonitoringMDB.ORB, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinessEventMonitoringMDB.Validator, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinessEventMonitoringMDB.ValidatorFactory] 
      service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinssEventForPersistenceMDB (missing) dependents: [service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinssEventForPersistenceMDB.ValidatorFactory, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinssEventForPersistenceMDB.ORB, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinssEventForPersistenceMDB.HandleDelegate, service jboss.naming.context.java.comp.xxxx-ear.xxxx-ejb.BusinssEventForPersistenceMDB.Validator] 
....
ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.3.Final "Arges" started (with errors) in 12188ms - Started 550 of 738 services (88 services failed or missing dependencies, 97 services are passive or on-demand)

Any help would be great.

Thanks

[ctomc]

can you pust output of

jar tf <name-of-deployment>

mostly i would like to see what jars do you have in WEB-INF/lib

--

tomaz

[ks-appendium]

Hi Tomaz,
As it turned out, the warning about the

Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to exception:

was a red herring.

The solution was to change the order of which the various modules were being started. In our case, we were starting the WAR before the EJB jar and that did not seem to matter with Spring 3.1 but the order seems to matter with Spring 3.2. Making sure that the EJB jar is started before the WAR fixes the issue.

Thanks