[enhydra] jvmRoute effect on JSESSIONID

Hi everyone,
  Having recently been thrown head first in the pond of Enhydra/Tomcat 
configuration without having a chance to get my feet wet, I'm feeling slightly 
disoriented.
  I'm trying to configure two Enhydra instances such that the session IDs will 
have information that allows mod_jk on an Apache server to keep session 
affinity, when balancing requests between the two Enhydra instances.
  Having configured an Enhydra server from scratch, I've set the jvmRoute 
attribute to "jvm1" on one of the servers' Engine element and I noticed (using 
jsp-examples/cart) that JSESSIONIDs from that server have ".jvm1" appended to 
them.
  However, I've modified an existing configuration (added the jvmRoute as 
above) and the JSESSIONIDs don't have the value of that attribute appended to 
them. Any idea on what could be preventing that? Should the jvmRoute Engine 
attribute be enough, regardless of the other configuration settings?
  The way that the value of the jvmRoute attribute is appended to JSESSIONID is 
compatible with both mod_jk and mod_jk2 for use with sticky sessions?
  I'm using Enhydra 6.4-1 (Linux).
  Thanks in advance,

    -- Edgar Alves


--
You receive this message as a subscriber of the enhydra@xxxxxxxxxxxxx mailing 
list.
To unsubscribe: mailto:enhydra-unsubscribe@xxxxxxxxxxxxx
For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws