That's the catch. Everything is A ok. no error what soever before I get
a null params.
Would an invalidated request still had the getRemoteAddr() and
getRequestURI() set?

And if so... how can I know if a REQUEST gets invalidated??

Jean-Philippe B�langer
CGI



Filip Hanik wrote:

>hmm, could it be that your Request gets invalidated,
>
>the Request you are holding on to is just a fascade.
>On top of my head, I can't see a connection with the cluster.
>Does your logs indicate anything else, like a null pointer etc?
>Filip
>----- Original Message -----
>From: <jean-philippe.belanger@(protected)>
>To: "Tomcat Users List" <tomcat-user@(protected)>
>Sent: Tuesday, January 13, 2004 9:24 AM
>Subject: Re: WAS: tomcat 5.0.16 Replication
>
>
>I've tried to replicate the problem with a simple servlet. outside of
>our MVC architecture (controller). and seams like I can't.
>
>I've put traces in our controller on the doPost method writing the
>request parameter to the console.
>When the 2nd node is shutdown, they request params become nulls! even if
>the same Post is done from a local static webpage.
>
>I've been trying to find out why for hours. but seams like I'm getting a
>dead-end soon.
>any ideas where I could look? fresh ideas would help! :)
>
>Jean-Philippe B�langer
>CGI
>
>
>Filip Hanik wrote:
>
>
>
>>interesting, never seen that, let me take a look. I have an automated test
>>that I run to check replication integrity.
>>since you get this everytime, it shouldn't be a problem for me to do
>>reproduce this.
>>do you by any chance have the test program you have and would email it to
>>me?
>>Filip
>>  
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
>For additional commands, e-mail: tomcat-user-help@(protected)
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)