unsubscribe
Hi,
I use TOMCAT 3.2
I tried to invalidate a session by calling HttpSession session.invalidate()
The session is not really invalidated. If the user clicks he does not get the same
sessionId (with request.getSession(false)) as before the invalidtae() call:
but he gets a session with another
Hi,
Does anybody know the following problem?
I use TOMCAT 3.2 and IE Explorer 5.
I call a servlet URL.
If I delete the 'temporary Internet files' (=cache) in IE Explorer the following
printout does not occurr.
But if I call my servlet a second time without having deleted the cache
(the image
Hi,
I am using TOMCAT 3.2 (I guess this means 3.2.1)
When creating a session (request.getSession(true)) within a servlet this session
creation takes about 10-20s!
And if you run the Netscape Browser 4.7 on the same machine as the servlet engine, the
session creation takes about 1 hour:
the
To be exact it takes 12 minutes to login (=create session) when running Netscape
browser and the TOMCAT servlet engine on the same machine.
Axel Lannion/France
-Original Message-
From: Bartsch Axel [SMTP:[EMAIL PROTECTED]]
Sent: mercredi 28 f vrier 2001 14:34
To: [EMAIL PROTECTED
Hi,
I am using TOMCAT 3.2 (I guiess 3.2 means 3.2.1).
When a servlet forwards a request to a JSP
using
ServletContext sc = getServletContext();
RequestDispatcher rd = sc.getRequestDispatcher("/common/index.jsp");
rd.forward(req,resp);
always this exception arrives: