4 Replies Latest reply on May 17, 2002 1:52 PM by adrian.brock

    fail to connect to management console

    eddy

      Hi,

      We are doing stress testing against JBoss 2.4.4; however, JBoss seems hung unexpectly. Sometimes, it hungs, after 20000 requests. Sometimes, it hungs, after 15000 requests. After it hungs, I can't even get connection to management console (localhost:8082). Also, all the jndi lookup call is frozen. I can't even do a java thread dump (kill -3 pid). Does anyone have the same experience before?

      Thanks,
      Eddy

        • 1. Re: fail to connect to management console

          Which OS/VM?

          Sounds like you've run out of a resource?
          Probably threads?

          Do you have any errors log/server.log ?

          I remember somebody posting something in January about a
          problem with a faulty external JNDI context. It
          blocked jndi until the external context
          timed out (about 20 mins). This was on Redhat 7.2
          I doubt this would cause port 8082 to drop connections.

          Regards,
          Adrian

          • 2. Re: fail to connect to management console
            eddy

            I am running on AIX 4.3 and IBM Jdk 1.3.

            Here is the attached server.log file, but I don't see any error inside. Also, no exception has been thrown in the console, it just hung. I do set up an external jndi context to connect LDAP server. Do u think that is the problem?

            Thanks
            Eddy

            • 3. Re: fail to connect to management console
              eddy

              I am running on AIX 4.3 and IBM Jdk 1.3.

              I can't attach the server.log file, since the file is too big. However, I don't see any error inside. Also, no exception has been thrown in the console, it just hung. I do set up an external jndi context to connect LDAP server. Do u think that is the problem? The following is my configuration to set up the external jndi context inside the jboss.jcml file:


              external/ldap/iplanet
              gos.ldap
              javax.naming.ldap.InitialLdapContext
              true
              false


              And the gos.ldap file:
              java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
              com.sun.jndi.ldap.connect.timeout=1500
              java.naming.provider.url=ldap://itchy:3389/o=seitel
              java.naming.security.principal=cn=root
              java.naming.security.authentication=simple
              java.naming.security.credentials=none


              Thanks
              Eddy

              • 4. Re: fail to connect to management console

                The problem with the external context occurs when the
                lookup neither suceeds or fails, it just hangs.

                The timeout property you have configured isn't
                supported until java 1.4 see section 3.4 below

                http://java.sun.com/j2se/1.4/docs/guide/jndi/jndi-ldap.html#PROP

                Regards,
                Adrian