I decided (in response to your email) to display the maxInactiveInterval. I nearly
fell off my chair when I saw the console read '60 seconds'!!
This was a case of the source control not managing what's on the Tomcat server.
Source control's web.xml read
<session-config>
<session-timeout>30</session-timeout>
</session-config>
But Tomcat's version read
<session-config>
<session-timeout>1</session-timeout>
</session-config>
Thanks. I'll now go and crawl into my hole.
Sri
-----Original Message-----
From: Hajratwala, Nayan (N.) [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 26, 2002 2:16 PM
To: 'Struts Users Mailing List'
Subject: RE: Hesitation leads to NullPointerException
are you sure that you haven't set the session timeout to 30 *seconds*?
Be careful to notice what the units being used by the timeout parameter are...
(minutes, seconds, milliseconds, etc)
---
- Nayan Hajratwala
- Chikli Consulting LLC
- http://www.chikli.com
-----Original Message-----
From: Sri Sankaran [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 26, 2002 11:54 AM
To: Struts-User
Subject: Hesitation leads to NullPointerException
Using Struts 1.0.2 on Tomcat 4.0.2
<bizarre.alert>
I have a problem that only occurs if the user lingers on a page for a while (say a few
minutes). If after this duration, the user triggers any action, the application
crashes with a NullPointerException.
I have debugged the exception as being caused by a null property of the form
bean. The question is this: how did the list get to be null. Why does it
become null only if the user lingers?
The form bean (ProductsListBean) contains :
private ArrayList products;
public List getProducts() { return products; }
This list is used to display a collection of products for the user to select (so, I
know that the list is non-null & non-empty). In the processing of the user action,
the following logic can be found
...
List products = productsListBean.getProducts();
Iterator iterator = products.iterator();
...
Obviously, (since the list is null) the application throws the exception at the second
line above.
</bizarre.alert>
Since the stack trace on the browser didn't indicate the "Root Cause" I went looking
for the Tomcat log -- it said the same thing that was on the browser. No more
information.
BTW my session timeout is set to 30 minutes and the this problem presents itself if
the user pauses for 2-3 minutes.
Sri
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
