When you copy a WAR or EAR file to the deploy directory, if the file is fairly 
large and takes a while to copy, it could be that JBoss attempts to hot-deploy 
the new file befoe it is fully copied.  This could result in the error message 
that you are seeing.

So the solution is to copy the WAR/EAR file to a temporary directory on the 
same disk as JBoss, and then to move the WAR/EAR file to the JBoss deploy 
directory (with possibly removing the existing EAR/WAR file first).

An alternate solution is to change the hot deploy scan time.  Change the value 
for "ScanPeriod" for the "URLDeploymentScanner" in the jboss-service.xml file.  
Of course, you could still occasionally end up with JBoss scanning the deploy 
directory at the same time that your EAR/WAR is being copied.

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3905908#3905908

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3905908


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to