Hi Mark, Thanks for the quick response.
>I suspect some sort of configuration issue. A guess would be that JBoss
>EAOP isn't configured to append the jvmRoute (to use the Tomcat
>configuration setting name) to the session ID.
I configured IE to show prompt when cookies are set. I can see the jvmRoute
value in JSessionID generated, with the format {someID}.{workerName}.
>You may need to look at the access log and/or network traffic to see
>what is going on. That usually sheds some light on these sorts of issues.
I cross verified the access logs. One thing I noticed is consistently the
request switches between servers. So, every time the server gets request, a
new session (JSESSIONID) is being sent out.
>From the network side too, no special rules are setup.
With same jvmRoute and network settings, sticky session works properly when I
use Jboss 6.4 version and 32-bit DLL.
If the 32 bit DLL has to work fine with Jboss7.2, then I get a feeling I am
missing something, but not able to figure out exactly what the issue is.
Please let me know if there are any particular configurations that need to be
checked.
Regards,
Saravanakumar.
smime.p7s
Description: S/MIME cryptographic signature
