Home JBoss howto Configuration How to deploy an exploded application on JBoss safely ?
30 | 07 | 2010
JBoss 5 AS Book
"JBoss AS 5 development" reviews
Please share your feedback/review with other readers!
Banner
Dashboard
Advertise with Us
Banner
RSS Feed
Java EE 1.6 resources
Login
Sign here for the NewsLetter.



JBoss admin resources
Banner
Java EE 1.6 resources
JBoss howto

How to avoid the 50 seconds start up limit in Eclipse ?

JBoss recipe of the day ...
Read More

How can you solve deployment errors caused by large war/jar/ear files ?

jboss recipe of the day ...
Read More

How do you configure your .war to be deployed after your EJB ?

jboss recipe of the day ...
Read More
How to deploy an exploded application on JBoss safely ?
Written by Mark S.   
JBoss recipe of the day

Have you ever tried to deploy a large application as exploded directory ? one common issue arises from the fact that if JBoss reads the deployment descriptors before the whole application is deployed. JBoss usually complains that the application was deployed as incomplete application.
This can happen for example if you are transferring the files on a slow network, or if the application is quite big.

One workaround is not to copy files but rather moving

mv mylargeapp.ear $JBOSS_HOME/server/default/deploy

why this should work ? because on most OS mv is treated as an atomic operation, that is, files are made available only when the transfer is completed (like for example when we issue a commit to the database).

I cannot guarantee that this will work on all situations (for example on the HP docs I have read that mv is atomic only within the same filesystem. Across filesystems mv is not atomic.)...however it's worth a try, isn't it ??


JBoss.org Search
Custom Search
Comments
Search
Only registered users can write comments!

3.26 Copyright (C) 2008 Compojoom.com / Copyright (C) 2007 Alain Georgette / Copyright (C) 2006 Frantisek Hliva. All rights reserved."