-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
I have a setting in with there's one apache 1.3.6 running and two JServ
1.0 instances all on the same machine. I've started both JServs manually
and the load balancing seems to work nicely, but there are problems with
sessions when I kill one of the JServs:
- client comes to my apache-site, requests a servlet
-> apache routes client to Jserv 1
- new session, client needs to log in (login/passwd)
-> get session-id = 3fc28f4de242b368.1.934485334173.JS1
-> JServ 1 killed
-> Clients session data lost (if not stored in disk)
- client requests same servlet again
-> Apache routes client to JServ 2 (which is running)
-> new session is created, client needs to log in again
- client gets new session-id: 3feeaccb6388286d.2.934485391511.JS2
(JS1 -> JS2 not the only change in that!)
When the client gets in contact with Jserv 2, he has an old session-id
cookie with him but no session object in Jserv 2, so Jserv 2 creates a new
session for him (not what I wanted). If any JServ developers read this, I
would be most pleased if someone creates a possibility of a session-data
'share', from where Jserv 2 could fetch the old session-data linked to
that 'dead' session-id! This would require some sort of 'distributed
shared memory' -solution, database or some other other container. Load
balancing would be much more fault tolerant after that.
Tommi
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
