Bugs item #834021, was opened at 2003-11-01 06:23 Message generated for change (Comment added) made by wesgere You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=834021&group_id=22866
Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Steven Grimm (koreth) Assigned to: Nobody/Anonymous (nobody) Summary: Original jarfile is kept open in exploded EAR Initial Comment: This happens with both 3.2.1 and 3.2.2. The attached zipfile contains an exploded .ear directory with a utility jarfile at the top level. The .war directory's manifest references the utility jarfile in its manifest classpath. JBoss makes a copy of the utility jarfile, but it seems to not close the original file, which means that on Windows it's impossible to delete or rename the .ear directory when I want to redeploy the application. On UNIX that's not an issue since you can delete open files. Running Process Explorer (an lsof-like tool for Windows, see www.sysinternals.com) confirms that JBoss has open file handles on both its temporary copy of the utility jarfile and the original. If I use a file rather than an exploded directory for my .ear, I can redeploy to my heart's content, but I'd really rather use an exploded directory (easier to update JSPs at runtime, etc.) To reproduce, unpack the zipfile into a running server's deploy directory on a Windows box, wait a few seconds for it to deploy, and then try to delete the .ear directory. You'll get a "file is in use" error. ---------------------------------------------------------------------- Comment By: Wes Gere (wesgere) Date: 2004-03-31 00:30 Message: Logged In: YES user_id=690357 I tested this using 3.2.1, and then using the lastest code base, and the behavior has changed, but the new behavior doesn't solve your problem. Now, when you deploy an exploded .ear, it no longer copies the files in the ear to the temp area - it uses the files directly from the original location (jar files referenced in war manifests, like your utility.jar, do get copied individually to temp area for some reason, but the files are not kept open and can be deleted). So it's more consistent and logical now, but you are still stuck with the jar files being deployed into the Java classloader directly from the original location. Of course, even though you can't delete/rename the .ear directory, you can overwrite the files inside it to redeploy (including the .jar files), but I assume you know that and prefer to delete/rename instead. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=834021&group_id=22866 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
