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
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