Configuration/Code: ================== Cluster -> 2 Appservers (Websphere 4.0 SP 4) and 1 Webserver Cluster Mode -> Round Robin Session Persistance -> Database Session Persistance Mode -> Medium Single Row Code -> One of our session object implements the "HttpSessionBindingListener" interface and we have implemented the methods "valueBound" and "valueUnbound". In the "valueBound" event, we write login information into a log file and on "valueUnbound" also we write the logout information. All the login and logout information are stored in the file in their respective servers. Issue -> Summary : When more than one user logs into the application, login information is stored in different servers but when the session times out, the logout information of all the users is logged in only one server (wherever the first request was served) .
More detailed flow ============= 1. Two users logs into the system ( and User1 is served by Server1 and User2 is served by Server2) 2. Login information is logged into Server1 and Server2 respectively. 3. Both the user close the brower without initiating Signoff 4. Session timesout after sometime (say 15 Mins) 5. The logout information for both the users are stored in Server1 itself (instead what was exepected that User1's logout information will be stored in Server1 and User2's logout information will be stored in Server2) Can anyone help us out in figuring out this problem (Code / Websphere configuration). Regards, Sudharshan
subject: Issue with "valueUnbound" event on session timeout in WebSphere 4 cluster