bla
unsubscribe
session invalidate does not work
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 sessionId: somehow the invalidate() routine creates a new cookie with another sessionId. Strange is that I never created this sessionId before. Does anybody know about this? AxelLannion/France - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: TOMCAT 3.2 + session
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] > Subject: TOMCAT 3.2 + session > > 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 reason is that Netscape takes all processing time when waiting for a response >and therefore blocks the servlet engine process. > > Does anybody know this problem? > > And why does TOMCAT need so long to create a session? With JRUN this was no problem. >What can be done? > > In which TOMCAT version will this be corrected? > > > Axel Lannion/France > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
TOMCAT 3.2 + session
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 reason is that Netscape takes all processing time when waiting for a response and therefore blocks the servlet engine process. Does anybody know this problem? And why does TOMCAT need so long to create a session? With JRUN this was no problem. What can be done? In which TOMCAT version will this be corrected? Axel Lannion/France - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
TOMCAT: IOException
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 files are found on the hard disk) the following printout occurrs. But everything works fine. (Option in IE Explorer is 'check for newer versions of stored pages=every visit to the page') 2001-02-28 11:34:28 - Ctx( /swam ): IOException in: R( /swam + /images/mn-bg.jpg + null) socket write error (code=10053) 2001-02-28 11:34:29 - Ctx( /swam ): IOException in: R( /swam + /images/mn-surpas s_hiq.gif + null) socket write error (code=10053) 2001-02-28 11:34:29 - Ctx( /swam ): IOException in: R( /swam + /images/mn-Drahtk ugel_80.gif + null) socket write error (code=10053) AxelLannion/France - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
forwarding to JSP + session not found in JSP
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:
2001-02-27 05:44:50 - ContextManager: SocketException reading request, ignored -
java.net.SocketException: Connection reset by peer: JVM_recv in socket input st
ream read
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:90)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:190)
at java.io.BufferedInputStream.read(BufferedInputStream.java, Compiled C
ode)
at org.apache.tomcat.service.http.HttpRequestAdapter.doRead(HttpRequestA
dapter.java, Compiled Code)
at org.apache.tomcat.core.BufferedServletInputStream.doRead(BufferedServ
letInputStream.java, Compiled Code)
at org.apache.tomcat.core.BufferedServletInputStream.read(BufferedServle
tInputStream.java, Compiled Code)
at javax.servlet.ServletInputStream.readLine(ServletInputStream.java, Co
mpiled Code)
at org.apache.tomcat.service.http.HttpRequestAdapter.readNextRequest(Htt
pRequestAdapter.java:129)
at org.apache.tomcat.service.http.HttpConnectionHandler.processConnectio
n(HttpConnectionHandler.java:195)
at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java,
Compiled Code)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java
, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
Additionally: the session, created in the servlet is not found in the JSP
Who can help?
AxelLannion/France
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
