Details
Description
I use cargo to start an standalone JBoss (using zipUrlInstaller) and then cargo:deploy to deploy an EAR file (about 14MB). The deployment of the EAR fails undeterministicly, with the JBoss printing
22:43:22,235 ERROR [MainDeployer] Could not initialise deployment: file:/home/continuum/working-directory/complete/checkout/test/webtest/target/jboss4x/home/deploy/ear-0.0.1.ear
org.jboss.deployment.DeploymentException: No META-INF/application.xml found
at org.jboss.deployment.EARDeployer.init(EARDeployer.java:133)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:861)
...
I guess this is because the JBoss tries to start the EAR before the copying is finished.
Unfortunately, this happens quite often on our continuum machine (which is a bit slower, ~1.6GHz). One solution (at least for post-FAT filesystems) would be to copy the file somewhere else and create a (symbolic) link to it.
Another way would be raise the ScanPeriod property in the jboss-service.xml
Issue Links
- depends upon
-
CARGO-859
JBoss remote deployer doesn't work with a large war file
-
This has been stabilized by
CARGO-859