Bug report #310 has just been filed.

You can view the report at the following URL:

   <http://znutar.cortexity.com:8888/BugRatViewer/ShowReport/310>

REPORT #310 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: webbug
State: received
Priority: high
Severity: critical
Confidence: public
Environment: 
   Release: tomcat 3.1 and 3.2beta6
   JVM Release: jdk1.3
   Operating System: windows
   OS Release: 2000
   Platform: server

Synopsis: 
http session is invalidated too frequently.

Description:
I am using TOMCAT as our JSP referenced implementation. We have several JSP's being 
used in a single web session and we use a Java Bean with session scope using the 
<jsp:useBean...> tag. The problem is that the http session gets invalidated between 
JSP requests for some unknown reason and the Java Bean is lost. Any reference to the 
bean raises a null pointer exception.

How can I prevent the http session from being invalidated so frequently? it happens to 
1 out of 6 requests. Is this a bug in TOMCAT? how do I work around this?

Thanks.
Title: BugRat Report # 310

BugRat Report # 310

Project: Tomcat Release: tomcat 3.1 and 3.2beta6
Category: Bug Report SubCategory: New Bug Report
Class: webbug State: received
Priority: high Severity: critical
Confidence: public

Submitter: David Dwyer ( [EMAIL PROTECTED] )
Date Submitted: Oct 26 2000, 08:36:32 CDT
Responsible: Z_Tomcat Alias ( [EMAIL PROTECTED] )

Synopsis:
http session is invalidated too frequently.
Environment: (jvm, os, osrel, platform)
jdk1.3, windows, 2000, server

Additional Environment Description:
This occurs with both TOMCAT 3.1 and 3.2 beta 6.

Report Description:
I am using TOMCAT as our JSP referenced implementation. We have several JSP's being used in a single web session and we use a Java Bean with session scope using the tag. The problem is that the http session gets invalidated between JSP requests for some unknown reason and the Java Bean is lost. Any reference to the bean raises a null pointer exception. How can I prevent the http session from being invalidated so frequently? it happens to 1 out of 6 requests. Is this a bug in TOMCAT? how do I work around this? Thanks.

View this report online...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to