Hi ,
 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  
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 
-----Original Message-----
From: Veniamin Fichin [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 15, 2004 3:28 PM
To: Tomcat Users List
Subject: Re: SESSION PROBLEM in UNIX


MUKUND Premchander wrote:

> Thank you for your reply .
> 
> I use IE 6 as my browser in windows and tomcat on HP unix.
> I meant that ,all I did was open a browser window load my application,

> goto a particular page Set page to refresh for every 10 secs( 
> application had a combo box to set interval of refresh).After few 
> refresh I get a null pointer exception and realize that the session is

> null suddenly .( I repeat I don't get this issue when I run tomcat in
> windows)

    Anyway, first try to localize the problem, there are some ways:
* implement javax.servlet.http.HttpSessionListener interface to see 
what's happening with your sessions;
* install RequestDumperFilter filter into your application to see every 
request and response data;
* sniff HTTP traffic (don't know how...)
* try another browser (I don't force you to throw IE, just try another 
one), for example Mozilla has excellent tool named "Live HTTP headers" 
which shows all HTTP request/response headers.

    That way you will see if a session invalidates normally for whatever

reason or it "lost" somehow.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to