BorlandTalk.com

Ted Cohn · Guest

We have upgraded to JBuilderX Enterprise and cannot get JBoss 3.2.2 to
launch successfully using just an empty project. We have determined the
culprit--JBuilderX spits out the following define in its launch script upon
running the project:

-Djava.io.tmpdir=C:/jboss-3.2.2/server/default/tmp/deploy/server/default/dep
loy/work

Turns out this directory does not exist, nor is it automatically created.
When I create the directory path manually, JBoss launches successfully the
first time from JBuilder. Subsequent launches, either JBoss or JBuilder
purges the tree somewhere below "tmp". We cannot find where this attribute
(java.io.tmpdir) is defined anywhere in JBuilder. It's a complete mystery.
Running JBoss's standard run.bat or run.sh script works fine without
specifying java.io.tmpdir.

Note: JBX says it only supports JBoss 3.2.1, but this version of JBoss does
not appear to be available from www.jboss.org. Also, JBuilder seems to also
say it supports 3.2x. Somewhat conflicting version specification!

Any immediately help would be greatly appreciated. Thanks,

Ted Cohn
Audio-Ex Inc.
[email]tcohn (AT) audio-ex (DOT) com[/email]

shushamen · Guest

Ted the workaround for your problem is simple:

In Jbuilder Go to tools - configure server - Jboss 3.x+ , click on vm
parameters and insert the following line at the beginning:

-Djava.io.tmpdir=C:/temp/jboss ( replace the path for the directory
you want to use jboss for some temporay files)

This line override the default configuration that jbuilder send to
jboss.

Currently I use jboss 3.2.3 without any problems and if you need to
get a specific version of jboss go to sourceforge.net/projects/jboss
-> files

"Ted Cohn" <tcohn (AT) audio-ex (DOT) com> wrote