This content has been marked as final.
Show 4 replies
-
1. Re: Deployment Problem -- Unable to replace existing file
peterj May 15, 2008 11:05 AM (in response to rajeevdr)This is a known issue with 5.0.0.beta4 - it tends to lock files on Windows. Probably related to the new virtual file system. Until the next version comes out, you will have to restart the app server if you want to redeploy anything.
-
2. Re: Deployment Problem -- Unable to replace existing file
rajeevdr May 16, 2008 3:18 AM (in response to rajeevdr)Thank you very much Peter. This issue was eating my head from quite some time.
__________
Regards,
Rajeev R. -
3. Re: Deployment Problem -- Unable to replace existing file
rweed Jun 14, 2008 2:00 AM (in response to rajeevdr)I had the file locking issue on Windows with 5.0.0.beta4, so I tried the Linux version and there is no locking problem there.
JBoss goes through the undeploy/deploy process, BUT it is still accessing the old classes. SO, under Linux, you still need to restart the server to effect your changes even without the file locking issue. -
4. Re: Deployment Problem -- Unable to replace existing file
tarch82 Jun 27, 2008 2:31 AM (in response to rajeevdr)"rweed" wrote:
I had the file locking issue on Windows with 5.0.0.beta4, so I tried the Linux version and there is no locking problem there.
JBoss goes through the undeploy/deploy process, BUT it is still accessing the old classes. SO, under Linux, you still need to restart the server to effect your changes even without the file locking issue.
I have the same problem of rweed with Linux...this is quite annoying, mainly because of the long start time. Is there some known workaround?
Thank you in advance,
bye Tarch!