tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Tomcat Going down Frequently
Date Wed, 17 Nov 2010 16:36:03 GMT
Hash: SHA1


On 11/16/2010 6:24 PM, Pid wrote:
> On 16/11/2010 21:15, Christopher Schultz wrote:
>> 2. There is no way for a client to check the validity of an HttpSession
>> object before calling getAttribute (or setAttribute for that matter)
>> The HttpSession interface javadoc says "For session that are invalidated
>> or expire, notifications are sent after the session has been invalidated
>> or expired." which means that, at least, the state above is correct.
> The class is calling: StandardSessionFacade.getAttributeNames.
> Shouldn't we see the HttpSession class in the stacktrace, not the
> implementation, if that's what they're calling?  Makes me think the OP
> is interacting with Tomcat internal classes.

No, HttpSession is just an interface, so you'll never see it in a stack
trace. Instead, you see the class that implements that interface.

N.B.: the HttpSession documentation says that IllegalStateException will
be thrown when calling getAttributeNames on an invalidated session. I
guess objects such as the LoginBean should expect that the session might
be invalidated, and catch IllegalStateException in those cases.

- -chris
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla -


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message