Following the instructions in the coherence online documents and coherence training labs, I packaged a simple web application "counter.war", deployed on the
tomcat6.0 on two different nodes(windows), and used webInstaller.jar to inspect and install the coherence*web, then restarted the two tomcat instances,
I can see the output messages indicating that the coherence is enabled, also I successfully tested the web application individually,everything is ok, BUT, when
I started the coherence loadbalancer and try to test the session distributed cache, problem happened:

First of all, i can see the load balancer routing to a specific node, and the output is right. then i killed the node using ctrl-c, i can see messages on the other node
indicating that it has restored backup partitions, but when i refresh the web page , i can see the load balancer re-route request to the second node, but the
counter value didn't increment properly. After debug and trace, I found the second node could get the right session (whick means the result of "request.getSession(true).isNew()" return false, and the session.getId() returns is exactly equal to the session id generated on the first node, but the application could not get the right attribute , "session.getattribute("xxx")" returned null.

So, my question is , the session objects seems partitioned successfully whilt one node killed, but why the attributes in the session couldn't be got successfully?

Enviroment:
Coherence 3.4.2/3.5.1/3.5.2 (all tested,got the same result)
Tomcat 5.5.28/6.0 (all tested)
OS: Windows XP

Any suggestions or successfully tested demos are highly appreciated!

BTW: I've tested the same application on Jetty, everything works well, the operation steps are same, so i'm confused....