1 Reply Latest reply on Jul 24, 2009 11:45 AM by Vladyslav Kosulin

    Problem with sticky sessions in JBoss 5.1.0.GA

    Vladyslav Kosulin Newbie

      Hi all,
      I do migration from 4.2.1 to 5.1.0.GA, and sticky sessions are not working with 5.1.0:
      I have a cluster of 2 JBosses with Apache mod_jk 1.2 front-end. After I start both JBosses, I see requests from the same session redirected to both boxes, and I frequently see messages like this one:

      11:20:37,175 WARN [CacheListener] Possible concurrency problem: Replicated version id 74 is less than or equal to in-memory version for session...

      According to JMX Console (jboss.web:type=Engine), jvmRoute values are set properly: wsc-voo-218, and wsc-voo-219.

      Here is my config:

       <Connector protocol="AJP/1.3" port="8009" address="${jboss.bind.address}"
       maxThreads="250" redirectPort="8443" />
       <Engine name="jboss.web" defaultHost="localhost" jvmRoute="${cpportal.jvmRoute}">

      And here is how I set jvmRoute through start-up parameter (for this box it is wsc-voo-219, and for another one - wsc-voo-218):

      JAVA_OPTS: -Dprogram.name=run.sh -server -Xms6144M -Xmx6144M -XX:MaxPermSize=3072M -Dcom.wsc.taxgard.envfile=custom.properties -Dsyslog.address=syslog -Dsys
      log.port=514 -Dlog4jdbc.drivers=com.sybase.jdbc3.jdbc.SybDataSource -Dlog4jdbc.sqltiming.warn.threshold=60000 -Dlog4jdbc.sqltiming.error.threshold=600000 -Dor
      g.jboss.resolver.warning=true -Djboss.partition.udpGroup= -Djboss.partition.name=Partition1001 -Djboss.messaging.ServerPeerID=2 -Djboss.server.name
      =taxgard -Dcpportal.jvmRoute=wsc-voo-219 -Djava.net.preferIPv4Stack=true

      For JBoss 4.2 I used to set
      <attribute name="UseJK">true</attribute>
      , but for JBoss 5.1. this is not required, and I do not do this.

      Did I miss something else?