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

    unexpected shutdown of JBoss

    tlt_bah

       

      "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.


        • 1. Re: unexpected shutdown of JBoss
          stefka

          I have a similar problem with Solaris 8.
          Have you found any solution?

          thank you

          • 2. Re: unexpected shutdown of JBoss
            expand

            We have the same problem with JBoss 3.2.5 running on Fedora Core 2. We already tried several 1.4 JVM's (Sun, JRockit, IBM).

            JBoss just shuts down unexpected.

            Some lines of the log:

            2005-03-18 11:52:33,194 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval:
            450000
            2005-03-18 12:00:03,196 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval:
            450000
            2005-03-18 12:00:24,250 DEBUG [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Notified to shutdown
            2005-03-18 12:00:24,251 INFO [org.jboss.system.server.Server] JBoss SHUTDOWN: Undeploying all packages
            


            Is there any way to track down the reason for this shutdown?

            • 3. Re: unexpected shutdown of JBoss
              expand

              Sorry forgot to turn on reply notification.

              • 4. Re: unexpected shutdown of JBoss
                bigdaddy

                I used to have the same jboss shutdown problems with Red Hat Enterprise Linux ES release 3. Try the following:

                Instead of running it as root, create a jboss user then run the following command.

                [root]# nohup su - <your jboss user> -c "${JBOSS_HOME}/bin/run.sh -c <your jboss server>" 2> nohup.out &

                Thanks.

                • 5. Re: unexpected shutdown of JBoss
                  aminlalji

                  I am encountering similar problems of Fedora Core 3, with JAVA 1.4.2_04... I tried running jboss under a jboss user, but the problem is, users who are not root can not access ports under 1024, therefore, HTTP, SSL, etc... get
                  denied... any ideas?

                  • 6. Re: unexpected shutdown of JBoss
                    mikek753

                    I have almost the same with JBoss 4.0.0 and 4.0.1SP1 on Solaris 8
                    and Linux.

                    any solution for that issue?
                    Does jboss account is required? I'm running jboss as root as
                    ./run.sh&

                    thanks