i tried to investigate this behavior to find out what went wrong and i've come up with
this information...when i open 2 browsers with difference of less than 1 minute on each
opening there session will both expire at the same time.
while if i open 2 browser with difference of more that a minute on each opening the
behavior seems fine...the first browser will timeout first then the second will follow
depending on the time the second browser was invoke which should be more than 1 minute.
by the way i'm using Tomcat 4.0 and jdk1.3.1
is this the behavior of Tomcat?..or part of its specification?
could someone enlighten me on this.
thanks a lot. =)
randie ursal wrote:
yes, it's really strange....i thought every session have there own context which means
if one has expired it won't affect the other..right?
actually i get the session id of every browser i open an it showed unique id for each..since
i opened each browser from IE shortcut icon.
the only thing that puzzled me is that when the other session has timeout the other would do the
same....i can say this because i set an attribute that implements session listener and when session
timeout all session id are displayed as invalidated.
hope someone has an idea on this.
Vikramjit Singh wrote:
-----Original Message----- From: randie ursal [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 10, 2002 1:30 AM To: [EMAIL PROTECTED] Subject: session timeout questionhi, could somebody explain to me what possibly went wrong about my application. what i did was, i set the maxInactiveIinterval time for 30 secs. on my servlet then i added to my HttpSession object an object that implements HttpSessionBindingListener so that i can keep track and see what happen when session expires. this scenario works fine, my session was invalidated after session timeout and the sessionlistener was notified. my problem is when i access my web application by using two browsers and let the 1st browser remain idle until session expires. the 2nd browser session also expires when 1st browser session expires i can say this because it put a trace line on valueUnbound of the sessionlistener object and two session id were displayed this was the session of both browser.Thats strange. Coz a new browser which you open, shall have associcated with it a new session.what went wrong with this? thanks a lot randie