To stick with the analogy:
Your session's baby part is: FEBA6A8127A69079C79B7A641158CE20 and
that remains the same if with daddy or mommy.
Your session's daddy part is: itchy
and
Your session's mommy part is: scratchy
Enjoy them :)
János
On Apr 3, 2009, at 5:32 PM, Roy McMorran wrote:
János Löbb wrote:
If You look the >>values<< created by the session earlier
with ...node1, than You will see the same values after fail over
with ...node2. A new session would not know about them.
To verify it You can use the supplied SessionExmaple webapp.
OK, trying that.
So, using an example webapp (see:
https://gillnet.mdibl.org/~mcmorran/session.jsp.txt
(which just uses session.getID() )
...should it return *just* the session ID part, or the concatenation
of the session ID and the jvmRoute?
Here's what I see:
Before failover:
This is the session id FEBA6A8127A69079C79B7A641158CE20.itchy
This is an existing session
After failover:
This is the session id FEBA6A8127A69079C79B7A641158CE20.scratchy
This is an existing session
Thanks,
-r
--
Roy McMorran
Systems Administrator
MDI Biological Laboratory
mcmor...@mdibl.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
