Good to know that this resolved your problem !.
I suppose you are now trying to failover the request, wherein subsequent
to load balancing your request got serviced from instance1 and thus
instance 1 has the session related to this client session. Now instance
2 would service the request, only if your request got failed over to
instance 2 (Ex: shutdown instance 1), and instance 2 now services the
request using the request session it has retrieved. Further for session
to be retrieved over other instance in the cluster you /need to deploy
your application with ---availability=true/ and use in-memory
replication ( configured out-of-box with cluster profile) support
provided by the web container.
Once you have deployed your application using this option. now test for
failover of request and session failover.
-/Pankaj
glassfish_at_javadesktop.org wrote:
> ok :D somehow its working. But:
>
> 1. I add some session value in instance 1 and cant see it in instance 2.
> 2. Sometimes when i want to run http://mocarz:80/clusterjsp i cant do it. Logs tell something about cluster in unHealthy. What to do with it?
> [Message sent by forum member 'freeq1986' (freeq1986)]
>
> http://forums.java.net/jive/thread.jspa?messageID=323606
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>