4 Replies Latest reply on Oct 3, 2012 5:09 AM by Niraj Salot

    JBOSS 7.0.2 Frequent Session Timeout

    Niraj Salot Newbie

      Hello all,

       

      We are currently having below mentioned deployment architecture

       

      1. 3 JBOSS Nodes
      2. 3 Apache Proxy Node - we're using mod_proxy and mod_proxy_balancer from apache
      3. 1 load balancer

       

      Apache to JBOSS communication happens through AJP. We have below mentioned AJP configuration

       

      <connector name="AJP" protocol="AJP/1.3" socket-binding="ajp" scheme="http" enabled="true" enable-lookups="false" max-connections="512"/>

       

      Our application is using GWT + spring + Oracle 11g Database.

       

      The communication between GWT & Spring happens with gwtrpc-spring Library.

       

      In our web.xml , we have session timeout set as 5 hours. But we are seeing that Users are getting random timeout during high load.

       

      We have "Timeout" value, which is currently set to 240 seconds in Apache Proxy Level.

       

      We have not changed any other JBOSS 7.0.2 configuration. Everything is kept as default in stanadalone.xml. Just we have adjusted our data source configuration.

       

      This is happening in our Production. So need help urgently.

       

      Thanks in Advance.

       

      Regards,

      Niraj Salot

        • 1. Re: JBOSS 7.0.2 Frequent Session Timeout
          Niraj Salot Newbie

          Hi,

           

          Checking further on this Issue , When I Fire

           

          curl --digest -D - http://admin:XXXXX@localhost:9990/management/ -d '{"operation":"read-resource", "include-runtime":"true", "address":[{"subsystem":"web"},{"connector":"AJP"}], "json.pretty":1}' -HContent-Type:application/json

           

          I get below mentioned output

           

          HTTP/1.1 200 OK

          Transfer-encoding: chunked

          Content-type: application/json

          Access-control-allow-origin: *

          Date: Tue, 02 Oct 2012 09:32:40 GMT

           

           

          {

              "outcome" : "success",

              "result" : {

                  "bytesReceived" : "21510543",

                  "bytesSent" : "368687830",

                  "enable-lookups" : false,

                  "enabled" : true,

                  "errorCount" : "385",

                  "max-connections" : 512,

                  "maxTime" : "182231",

                  "processingTime" : "5784419",

                  "protocol" : "AJP/1.3",

                  "requestCount" : "75681",

                  "scheme" : "http",

                  "socket-binding" : "ajp",

                  "ssl" : null,

                  "virtual-server" : null

              }

           

          How to see   "errorCount" : "385", ? I can not see anything in server log.

           

          Please help urgently.

           

          Thanks,

          • 2. Re: JBOSS 7.0.2 Frequent Session Timeout
            Tomaz Cerar Master

            Hi,

             

            errorCount also includes 404 errors...

             

             

            are there any exceptions that happens when session times out?

            Can you make sure sessionId cookie is passed at all this times?

             

            Just to make sure, can you add session listener that will log when session is beeing destroyed?

             

             

            --

            tomaz

            • 3. Re: JBOSS 7.0.2 Frequent Session Timeout
              Niraj Salot Newbie

              Hi,

               

              No there are not any exceptions that happens when session times out.

               

              We are making sure that cookie is passed at all this times.

               

              Thanks,Niraj.

              • 4. Re: JBOSS 7.0.2 Frequent Session Timeout
                Niraj Salot Newbie

                Hi,

                 

                More Information on this.

                 

                We already have  session listener but It is not getting invoked as this is what is happening.

                 

                Randomly the Apache server thinks that JBOSS is too busy OR it is down and It fwd. the requests to anothe Node of JBOSS which does not contain that session.

                 

                We are having stick session approach and for that it is must the subsequest request goes to the same node which generated session.

                 

                What could case Apache to take that session that JBOSS is too busy OR it is down?

                 

                Thanks,Niraj Salot.