6 Replies Latest reply on Mar 30, 2005 3:10 PM by Michael K

    unexpected shutdown of JBoss

    tlt_bah Newbie

       

      "tajhlande" wrote:
      We have a JBoss 3.2.1/Tomcat 4.1.24 bundle running on an UltraSPARC with SunOS 5.8, 2 GB RAM. Not many other processes running on the machine right now, so we have the CPU and other processes all to ourselves.

      For some reason, the JBoss server won't stay up. It will shut itself down within 1-18 hours of starting. The load on it doesn't seem to matter much, although since it is a test server it's not getting hit much, so its usually idle when it shuts down. We've tried starting it with nohup, i.e.:

      nohup ./run.sh 2>&1 > jboss.out &


      Doesn't help. The JBoss process doesn't seem to die, anyway, not when the user who starts it logs out or otherwise, but it does seem to be doing an orderly shutdown. Here's a snippet of the log:

      2004-01-20 18:20:24,660 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval: 450000
      2004-01-20 18:27:54,670 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval: 450000
      2004-01-20 18:27:54,675 DEBUG [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Using properties: {user=sa, password=}
      2004-01-20 18:27:54,677 DEBUG [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Using properties: {user=sa, password=}
      2004-01-20 18:27:54,678 DEBUG [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Using properties: {user=sa, password=}
      2004-01-20 18:27:54,680 DEBUG [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Using properties: {user=sa, password=}
      2004-01-20 18:27:54,682 DEBUG [org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory] Using properties: {user=sa, password=}
      2004-01-20 18:35:24,680 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval: 450000
      2004-01-20 18:42:13,668 INFO [org.jboss.system.server.Server] JBoss SHUTDOWN: Undeploying all packages
      2004-01-20 18:42:13,670 INFO [org.jboss.deployment.MainDeployer] Undeploying file:/projects/dcp/jboss-3.2.1_tomcat-4.1.24/server/default/deploy/management/
      


      So the rest of the log indicates an orderly shutdown. It appears that JBoss is receiving a TERM signal from somewhere, but we can't find anything or anyone that could be doing it. No exceptions, nothing of note except that it shuts down.

      My question: Is there some configuration quirk that would cause JBoss to shut itself down, during idle time or under some other condition? Any insight or advice in this matter would be helpful.