Great! That cut my startup time from 2:30 (best case) to 40 seconds. Thanks!
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867505#3867505
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867505
Thanks for the reply, Scott. I have modified run.conf to include
"-Djboss.deploy.localcopy=false" in the JAVA_OPTS variable. However, I'm still
seeing temp files created under tmp/deploy/, along with the corresponding
message "Attaching Java program to /server/default/tmp/deploy/tmp9xxx.jar"
Hi,
Is it possible to keep the deploy process from using "tmp" names when it copies
jars to tmp/deploy/, maybe through a configuration somewhere?
I ask because we are running JBoss (4.0.1) on an iSeries. Java on OS/400 has an
amusing little quirk: when it loads a class from a jar that it hasn't
Is this still possible? We can deploy an app into 3.2.6 with the following
structure:
SomeApp.ear/
| META-INF/
| application.xml
| SomeEjbs.jar/
| META-INF/
| ejb-jar.xml
| com/blah/blah/*.class
| SomeService.sar/
| META-INF/
Oh, and I second fbiaggi's advice: Make sure your system is all up-to-date on
PTF's (Java & others).
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859865#3859865
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859865
We run JBoss 4.0.0 on our iSeries, so no need to step back to the older
version. Just a couple of tips:
- Make sure you specify the correct JAVA_HOME in jboss-4.0.0/bin/run.conf (ours
is /QIBM/ProdData/Java400/jdk14)
- Make sure you give the VM enough memory in run.conf (at least 512 MB)
- If yo
