Bugs item #580636, was opened at 2002-07-12 16:21 Message generated for change (Settings changed) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=580636&group_id=22866
Category: JBossServer Group: v3.0 Rabbit Hole >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Scott M Stark (starksm) Assigned to: Nobody/Anonymous (nobody) Summary: Jetty should use the JBoss tmp dir Initial Comment: There have been a number of reports regaurding the content of unpackaged wars being removed and causing the web app to fail. One cause of removal is cron jobs cleaning out the system tmp directory which is what Jetty uses for its unpackaged wars. These should be placed into the JBoss server/<config-name>/tmp directory by default so that users have more control over this. ---------------------------------------------------------------------- Comment By: Jens Schumann (french_c) Date: 2003-06-21 17:59 Message: Logged In: YES user_id=661964 Glad I just repeated the summary. Stupid me. I was reading the follow ups only ;( ---------------------------------------------------------------------- Comment By: Jens Schumann (french_c) Date: 2003-06-21 16:56 Message: Logged In: YES user_id=661964 Most Unix platforms I know of default to /tmp for java.io.tmpdir. Hence this is a major problem since you will also have a default cron job which will wipe out old files from /tmp usually. So if you have web applications on your box which won't be touched that often (such as the JMX Console) you will run into FileNotFoundExceptions. ---------------------------------------------------------------------- Comment By: Greg Wilkins (gregwilkins) Date: 2002-09-19 10:09 Message: Logged In: YES user_id=44062 Alternately, shouldn't JBoss set the java.io.tmpdir property to be it's own temp directory? That way anything that uses temp File creation will use the right directory - including Jetty. ---------------------------------------------------------------------- Comment By: Mike Finn (mikefinn) Date: 2002-08-29 16:47 Message: Logged In: YES user_id=418562 This has been a source of irritation for me as well. This is how I have gotten around it. It's a hack, but you can "fool" Jetty to use any directory for its deploy tmp, just by overriding java.io.tmpdir (like with JAVA_OPT). Jetty appears to the the only thing in the source tree using java.io.tmpdir, and this does not seem to have any ill-effects. Of course, a more permanent solution is needed, but how to have Jetty read a *JBoss* config setting (like paths) in a portable manner? It seems overriding java.io.tmpdir might be the best solution, but where to do it? Main? Server? Mike ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=580636&group_id=22866 ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
