2 Replies Latest reply on Apr 21, 2003 12:08 AM by Jon Barnett

    JBoss 3.2 Tomcat is not coming up

    Sascha Newbie

      Hi,

      I'm running JBoss 3.2 Tomcat under Redhat Linux 7.3. When starting JBoss, the last message I see in the server.log file is
      INFO [org.jboss.naming.NamingService] Starting jnp server

      In boot.log:
      INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml

      No error messages. But the server is not running. I can't see anything on localhost:8080. And also if I use "jboss_init_redhat.sh stop" I get the error, that no server is running. But I can see a lot of java processes when listing them with "ps -e". I tried to change the debug level, but that doesn't helps me (ok, errors should be always logged).

      Can somebody help me?

        • 1. Re: JBoss 3.2 Tomcat is not coming up
          Sascha Newbie

          Some additions:
          Java is 1.4.1
          In server-config.xml I comment the webservice, because JBoss is not running further more (the same as described before) without any error message.

          • 2. Re: JBoss 3.2 Tomcat is not coming up
            Jon Barnett Master

            Sounds like the naming service is not starting up. You should get something like this for server.log (I have a logging threshold at INFO).
            2003-04-21 03:04:01,257 INFO [org.jboss.naming.NamingService] Starting
            2003-04-21 03:04:01,266 INFO [org.jboss.naming.NamingService] Starting jnp server
            2003-04-21 03:04:02,017 INFO [org.jboss.naming.NamingService] Started jnpPort=1099, rmiPort=0, backlog=50, bindAddress=null, ClientSocketFactory=null, ServerSocketFactory=null
            2003-04-21 03:04:02,181 INFO [org.jboss.naming.NamingService] Listening on port 1099

            I'd check that you can connect to port 1099 and whether there are any Linux security constraints on your boxen that would prevent binding to port 1099. I'm running on Redhat 7.2.