-
1. Re: Jboss-4.0.3SP1 shutting down itself without any explicit
Who has access to this machine?
It's possible to shut down the server through the JMX console as well. -
2. Re: Jboss-4.0.3SP1 shutting down itself without any explicit
Now the machine is on public IP and the jboss 8180 port is also public, therefore anybody can access it. But we faced this problem earlier when the machine was not on public IP.
-
3. Re: Jboss-4.0.3SP1 shutting down itself without any explicit
We are seeing the exact same problem, and we are also running jboss 4.0.3sp1. Did you ever get an answer about this?
-
4. Re: Jboss-4.0.3SP1 shutting down itself without any explicit
Just wanted to let you know we are also having the same issue...
Running JBoss 4.04GA on CentOS 4.4 using the included red hat run script (running JBoss as a service).
The problem happens about twice a month for us on the server which is on all the time.
On another spot in the forums and from this link: http://davidbolton.net/blog/?p=21
it looks like some people have had success adding the -Xrs option to their JAVA_OPTS in run.conf. We are just trying that now, will hopefully post in a couple months if we've avoided the problem since. -
5. Re: Jboss-4.0.3SP1 shutting down itself without any explicit
Unfortunately, JBoss shut itself down again today -- the -Xrs option is not helping my problem of JBoss shutting itself down.
Is this problem still happening for anyone?
Better yet, has anyone found a resolution?
A little more background:
- running 4.0.4GA
- running jdk 1.5_09-b03
- running CentOS 4.4
- using the jboss_init_redhat.sh script found in JBoss bin directory to start/stop server (we placed it in /etc/init.d and start/stop jboss with the following command: service jboss start).
- by default, jboss starts in runlevel 3 (which is what our server starts up in)
Like I said in the previous post, JBoss shuts down about once every two weeks (of otherwise continuous operation).
Our log files indicate a normal shutdown -- forceHalt: true etc etc, everything undeploys as if i called service jboss stop, and the shutdown is clean. Our server also shuts down when there is no load -- our load today was essentially nothing at all and the server shut down.
Am I doing something wrong with using the jboss_init_redhat.sh script? During development, I do sometimes start jboss from an SSH session, but on disconnect, jboss IS still running (and I thought it's like starting/stopping any other service, such as httpd, which is fine after doing so from an SSH session... ) (and a ps command yiels me '?' for the TTY for jboss's java process).
Thanks for any help, sorry to report the -Xrs option is NOT working for me...
Oh, and just to make sure it's clear, there's NO System.exit() calls in our code :-) (and the shutdowns happen when nothing is going on anyway)
-Mark -
6. Re: Jboss-4.0.3SP1 shutting down itself without any explicit
I'm having a similar problem here..
- Jboss v4.2.0GA
- Redhat EL 3.4.5-2
- jdk 1.5.0_04-b05
After around 2 months without having any problem, all of sudden jboss shut down:
*** LOG ***
19:56:54,521 INFO [Server] Runtime shutdown hook called, forceHalt: true
19:56:54,522 INFO [Server] JBoss SHUTDOWN: Undeploying all packages
********** -
7. Re: Jboss-4.0.3SP1 shutting down itself without any explicit
I have the exact same problem. Earlier it used to shutdown everytime I used to logout of my ssh session, now it stays up for a few days and then shutsdown automatically. I see the same message in my server.log file.
Log message: Runtime shutdown hook called, forceHalt: true
My environment: JBOSS 4.2.2. GA
Host: CentOS 5.0
JDK: jdk1.5.0_15
Start command: run.sh -b 0.0.0.0 &
Does anyone from the jboss community have a resolution for this? This is getting to be very frustrating.
Thanks,
Yasha
