In answer to my own question- while trying to get apache2/tomcat sticky sessions working as a workaround to my clustering woes- I set the jvmroute property in
to reflect the server/AJP port used eg:
Which fixed both problems- sessions were sticky as they had something to bind to, as mentioned elsewhere on this forum, but more importantly my clustered instances now had the jvmroute appended to their JSessionID to uniquely identify the object.
Previously I would imagine that each instance was searching for the exact same JSessionID key and only ever using their local copy of the session, but now that machine/port names are appended they recognise remote instances they might like to try to use.
I haven't found any mention of this in the JBoss clustering document, so be advised.
which version : mod_jk or mod_jk2?
This is under mod_jk2. I've got sticky sessions going fine now there's a jvmroute in there, although I was somewhat surprised that this also fixed my HttpSession clustering problems...