I am using tomcat 3.2 not tomcat 4.0 hence as per your suggestion I did try and implement HttpSessionBindingListener and put the object
into the session in the same jsp ,
the valueBound was called but when the session access threw null pointer
exception valueUnbound was not called
No-no, you need to implement HttpSessionListener, not HttpSessionBindingListener. The former interface will alert you when a session is created and destroyed, that way you will know if your session does away for example by container or just disappears, that's the bug. And still, try somehow to determine if JSESSIONID is passed with each request (use filter, HTTP sniffer or anything). If this cookie is passed, but session continuously lost, this must be the bug.
And 3.x version is now outdated a little, so may be there was a bug in session handling, but nobody will fix it these days. Consider upgrade to at least 4.x serie, that way you may hope someone will help you in case of trouble.
And when I gave a sop the request.getSession(false) printed the same
session object .
I did try with NN and I get the same problem .
Kindly help with your comments
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
