3 Replies Latest reply: Apr 18, 2012 5:18 AM by Radoslav Husar RSS

    AS7.1 - Exception acquiring ownership

    Maciej Lad Newbie

      Hi,

      This is my error:

       

      12:11:17,550 ERROR [org.apache.catalina.connector.CoyoteAdapter] (ajp--172.17.251.1-8009-21) An exception or error occurred in the container during the request processing: java.lang.RuntimeException: JBAS018060: Exception acquiring ownership of MNZ0PD6VNapv4O8cl3rIdqMh

              at org.jboss.as.web.session.ClusteredSession.acquireSessionOwnership(ClusteredSession.java:528) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final]

              at org.jboss.as.web.session.ClusteredSession.access(ClusteredSession.java:496) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final]

              at org.apache.catalina.connector.Request.doGetSession(Request.java:2625) [jbossweb-7.0.10.Final.jar:]

              at org.apache.catalina.connector.Request.getSession(Request.java:2375) [jbossweb-7.0.10.Final.jar:]

              at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:82) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final]

              at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.10.Final.jar:]

              at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.10.Final.jar:]

              at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.10.Final.jar:]

              at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.10.Final.jar:]

              at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:505) [jbossweb-7.0.10.Final.jar:]

              at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:445) [jbossweb-7.0.10.Final.jar:]

              at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.10.Final.jar:]

              at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03]

      Caused by: org.jboss.as.clustering.lock.TimeoutException: JBAS010223: Cannot acquire lock //default-host//GPWIS2/MNZ0PD6VNapv4O8cl3rIdqMh from cluster

              at org.jboss.as.clustering.lock.SharedLocalYieldingClusterLockManager.lock(SharedLocalYieldingClusterLockManager.java:439)

              at org.jboss.as.clustering.web.infinispan.DistributedCacheManager.acquireSessionOwnership(DistributedCacheManager.java:376)

              at org.jboss.as.web.session.ClusteredSession.acquireSessionOwnership(ClusteredSession.java:520) [jboss-as-web-7.1.0.Final.jar:7.1.0.Final]

              ... 12 more

       

      This is a configuration:

       

      AS 7.1 two nodes in cluster standalone-ha

      Apache 2.2.15 with mod_cluster 1.2 Final as LB

       

      LB conf:

      ProxyPass / balancer://cluster-uat/ stickysession=JSESSIONID|jsessionid nofailover=On

          ProxyPassReverse / balancer://cluster-uat/ stickysession=JSESSIONID|jsessionid

          ProxyPreserveHost On

       

      AS 7.1 conf:

       

        <subsystem xmlns="urn:jboss:domain:modcluster:1.0">

                  <mod-cluster-config advertise-socket="modcluster" sticky-session="false" balancer="cluster-uat">

                      <dynamic-load-provider history="9" decay="2">

                          <load-metric type="cpu"/>

                      </dynamic-load-provider>

                  </mod-cluster-config>

              </subsystem>

       

       

      node1:

      [standalone@172.17.251.x:9999 mod-cluster-config=configuration] ls

       

      ssl

      advertise=true

      advertise-socket=modcluster

      auto-enable-contexts=true

      balancer=cluster-uat

      dynamic-load-provider={"history" => "9","decay" => "2","load-metric" => [{"type" => "cpu","weight" => "2","capacity" => "1"},{"type" => "sessions","weight" => "1","capacity" => "512"}]}

      excluded-contexts=ROOT,admin-console,invoker,jbossws,jmx-console,juddi,web-console

      flush-packets=false

      flush-wait=-1

      max-attemps=1

      node-timeout=-1

      ping=10

      proxy-list=

      proxy-url=/

      socket-timeout=20

      sticky-session=false

      sticky-session-force=false

      sticky-session-remove=false

      stop-context-timeout=10

      ttl=60

      worker-timeout=-1

       

      node2:

      [standalone@172.17.251.2:9999 mod-cluster-config=configuration] ls

      ssl

      advertise=true

      advertise-socket=modcluster

      auto-enable-contexts=true

      balancer=cluster-uat

      dynamic-load-provider={"history" => "9","decay" => "2","load-metric" => [{"type" => "cpu"}]}

      excluded-contexts=ROOT,admin-console,invoker,jbossws,jmx-console,juddi,web-console

      flush-packets=false

      flush-wait=-1

      max-attemps=1

      node-timeout=-1

      ping=10

      proxy-list=

      proxy-url=/

      socket-timeout=20

      sticky-session=false

      sticky-session-force=false

      sticky-session-remove=false

      stop-context-timeout=10

      ttl=60

      worker-timeout=-1

       

       

       

      Please help me how to diagnose where is my problem.

       

      Stickysession set true not good because if one-node dies or shutdown i have 5xx error in http.