I try to make a shutdown without halting the JVM
with config.setExitOnShutdown(false);
But the system cannot stop properly the jboss-service.xml and jboss-jca.sar make a
ConcurrentModificationException (3.0.8 and 3.2.4)
an idea?
regards
View the original post :
http://www.jboss.org/index.html
Or, instead of hacking config files, you could run 'shutdown.bat' (or 'shutdown.sh')
with no parameters and discover that there's a '-s' option which appears to solve the
problem.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3840156#3840156
Reply to the pos
Hi,
on the Shutdown.jar you can find a jndi.properties
modify this file with your good IP adress or network name and the good port.
Also i found a solution to my problem on warpper use no delay at shutdown and wrapper
wait for the end of the shutdown.
regards
View the original post :
http://
My problem is the following:
Config:
RedHat ES 3.0
JBoss 3.2 with default server config
JBoss is binded to a specific IP address, not 0.0.0.0.
I start it with 'jboss_redhat_init.sh start'.
It starts successfully and listening only that IP address what I binded to.
But if I want to stop it with '
I try with javawrapper and this message appear when i shutdown my service:
INFO | jvm 1| 2004/06/11 10:40:23 | 10:40:23,552 INFO [HypersonicDatabase]
Stopping
ERROR | wrapper | 2004/06/11 10:40:30 | Shutdown failed: Timed out waiting for the
JVM to terminate.
ERROR | wrapper | 2004/06/