Corrections below:
On 1/8/07, Josh Rehman [EMAIL PROTECTED] wrote:
...
While there are [[hacky]] ways to notify the offline server of state changes
...
How can you have your cake and eat it too? You need some way for nodes
to see if they are participating in a distributed session [[on
what are your specific session settings? does resin know about your
load balanced cluster? or are you managing the load balancer outside of
resin and using resin to tie them together thru the db persistence? are
you using 'always-load-session?
Jacky wrote:
Dear all,
I have implemented
Hmm. I was reading:
http://www.caucho.com/resin-3.1/doc/tcp-sessions.xtp
Particularly the section under recovery which states:
When Host C restarts, possibly with an upgraded version of Resin, it
needs to use the most up-to-date version of the session; its
file-saved session will probably be
1. I start server A and login to my application
At this point, A will get your request and will become your primary
server, and B will be your secondary server.
2. I stop Server A and start Server B
3. I continue to work in the browser, my session stays intact and i
can proceed normally
At
