Removing a jsessionid for a soon to go invalid session

[Steve]

I have a purchased specialized search tool that cannot tolerate being
shut down before it completes its search, so when a user logs out of
our tomcat application session, I redirect them and then allow the
search to complete in a thread. At the end of that thread I invalidate
the session. The problem is that if the same user logs back in, they
are still using the
dying jsessionid and get attached to the session as it dies. I need
for them to get a new session. Is there any way to remove the
jsessionid cookie from the browser for a running tomcat session?

 

[Lew]

I have a purchased specialized search tool that cannot tolerate being
shut down before it completes its search, so when a user logs out of
our tomcat application session, I redirect them and then allow the
search to complete in a thread. At the end of that thread I invalidate
the session. The problem is that if the same user logs back in, they
are still using the
dying jsessionid and get attached to the session as it dies. I need
for them to get a new session. Is there any way to remove the
jsessionid cookie from the browser for a running tomcat session?

I have been taught not to create threads within a Web app.

What about session.invalidate()? That will kill the session but not the thread.

I assume that the logout of which you speak is via a user click. If they
simply close their browser or time out they won't be able to re-enter the old
session in any event.

If the search is running in its own thread and the app has already sent a new
screen to the user, how does the user get to see the search results? I figure
you must have solved that aspect, and that issue interests me.

- Lew

 

[Steve]

Hi Lew,
The "search tool" runs in its own tomcat and our webapp opens a
socket to it and exchanges XML. Then the search updates on our screen
are by AJAX.
As for session.invalidate(), that is what I do, but I have to wait
for the search to complete. I have to wait only because the "search
tool" can't handle a interrupted search.

Thanks,
Steve

 

[Lew]

Hi Lew,
The "search tool" runs in its own tomcat and our webapp opens a
socket to it and exchanges XML. Then the search updates on our screen
are by AJAX.
As for session.invalidate(), that is what I do, but I have to wait
for the search to complete. I have to wait only because the "search
tool" can't handle a interrupted search.

How does session.invalidate() interrupt the search?

- Lew