4 Replies Latest reply on May 17, 2006 9:07 AM by Börje Jonsson

    Jboss problem

    Börje Jonsson Newbie

      We have a problem when we performance test our application.

      When we run our Jboss app with a high load; 80-100% CPU load for more than 20-40 minutes, the whole Java process with Jboss hangs.
      Mostly it accepts no connection at all. Sometimes it allows http connection to the default webapp but no connection to our application.
      The only way to stop Jboss is through kill -9.

      We have an enterprise application consisting of several stateless session Beans. We are using Hibenate for persistance and Spring for configuration.

      Hibernate version 3.0.5
      Jboss version is 4.0.3SP1,
      Java version 1.5.0_06,
      Oracle JDBC driver,
      OS Red Hat ES3, (kernel 2.4.21).
      The Oracle database is on a separate server.

      I have successfully run Jboss and our application on slower servers (Windows XP and Suse Linux 10) with no problem.

      Is this a known problem, and more to the point; is this an operating system specific problem?

      Börje Jonsson

        • 1. Re: Jboss problem
          Vladimir Stefanyuk Newbie

          We have exactly the same problem. The only difference that we are using FreeBSD 6.0-STABLE,I386 and Java version 1.4.2-p7.

          The problem occurs exactly in the same way. When high loading, after some time app hangs (no activity of Java and DB server, 100% idle) and app do not response at all. We are using basic authentification, and even with a opening new connection, no login/password is appeared via browser, so it means that Tomcat hangs completelly and it is not about application or database connection.

          When we tried the same app by using Windows XP server by making a lot of high loading requests, app is slow, but never hangs.

          It is very critical problem for us :(

          • 2. Re: Jboss problem
            Elias Ross Master

            Can you get a stack trace?

            • 3. Re: Jboss problem
              Vladimir Stefanyuk Newbie

              Sorry, already can't. It was time-critical for us. Moved to the Windows OS, problem disapperied. Propably it was the problem of using 64-bit FreeBSD and 32-bit Java, seems an threads using specific problem.

              • 4. Re: Jboss problem
                Börje Jonsson Newbie

                Seems a lot of the problems is because of logging. The SocketHubAppender causes the most of the problems.

                A lot of threads is waiting for a lock:

                "http-" daemon prio=1 tid=0x671b8858 nid=0x5cf1 waiting for monitor entry [0x5ff97000..0x5ff98670]
                 at org.apache.log4j.Category.callAppenders(Category.java:185)
                 - waiting to lock <0x7160bb18> (a org.apache.log4j.Logger)

                One thread is waiting in socket write for some reason and makes all logging threads block.

                "http-" daemon prio=1 tid=0x08abd560 nid=0x5c8d runnable [0x688a4000..0x688a57f0]
                 at java.net.SocketOutputStream.socketWrite0(Native Method)
                 at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)

                found this by using kill -3 on the Java process.