28284 – Jboss temp directory incorrectly set.

Bug 28284 - Jboss temp directory incorrectly set.

Summary: Jboss temp directory incorrectly set.

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	All Linux

Importance:	High trivial
Assignee:	Matthew Kennedy (RETIRED)

URL:	http://www.jboss.org
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-09-09 11:48 UTC by Brett Simpson
Modified:	2003-12-20 00:50 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Brett Simpson 2003-09-09 11:48:14 UTC

In the /opt/jboss-3.2.1/bin/run.sh the following line 
 
JAVA_OPTS="$JAVA_OPTS -Dprogram.name=$PROGNAME" 
 
should be set to something like this 
 
JAVA_OPTS="$JAVA_OPTS -Djava.io.tmpdir=/opt/jboss-3.2.1/jetty 
-Dprogram.name=$PROGNAME" 
 
This tells Jboss to use /opt/jboss-3.2.1/jetty instead of /tmp to store deployed files. If 
/tmp get's cleaned it will hose jboss unless this change is made.

Comment 1 Eivind Tagseth 2003-10-21 01:32:50 UTC

Just got bitten by this myself.  The old ebuilds (version 3.0.2) used to
have the tmp directory settable in /etc/conf.d/jboss as JBOSS_TEMP_DIR, which
was used in the init-script to set -Djboss.server.temp.dir

JBoss is useless in a production setting without this change...

Comment 2 Matthew Kennedy (RETIRED) gentoo-dev

2003-12-18 07:13:55 UTC

any objections to setting it to /var/tmp/jboss/jetty?  (this is more of a r/w filesysttem than /opt)

Comment 3 Matthew Kennedy (RETIRED) gentoo-dev

2003-12-20 00:50:49 UTC

fixed with jboss-3.2.3 now in portage