The java session stays active until it times out, because each time you hit a page
a new http conenction is created, and the servlet engine will associate the
current java session with the new http session based on a cookie
or other attribute that identifies them. The Java session will usually time out if
it does not detect a http connection from its user.
have a look at HttpSessionBindingListener and HttpSessionBindingEvent as these
will allow you to catch when the java session times out, and lets you run
any cleanup code you need.
At 02:41 PM 22/11/99 -0800, you wrote:
>Hello-
>I am currently connecting to an AS/400 by using IBM's as400 jdbc access class.
>Once a user logs into the system, I store that connection in a session
>and use it for all the transaction's the user completes. Now, when a
>connection is established, I see a job running on the as400 for that
>user. Fine. When the user clicks the logout button, I invalidate the
>session and there are no more jobs running for that user on the 400.
>But if the user closes the browser without clicking the logout button,
>the job remains on the 400 and doesn't end. Is there something that
>I am doing wrong or missing. I would appreciate it if someone could
>give me some ideas/tips. Thank you.
>J
--
Subvert the dominant paradigm
http://www.cyber4.org/members/grumpy/index.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
