Pid * wrote:
>
>
> Exactly which version of Tomcat are you running?
>
>
Latest, 7.0.21.
--
View this message in context:
http://old.nabble.com/Request-params-randomly-null-in-servlet%28s%29-tp32461421p32474158.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
--
On 15/09/2011 14:46, Darius D. wrote:
>
>
>
> Pid * wrote:
>>
>>
>> What is your server.xml config? (please remove comments, passwords etc
>> & post it inline, in the response)
>>
>>
>
> Here it is, nothing special ( except usage of RemoteIpValve ). Thanks for
> looking into this problem.
>
Pid * wrote:
>
>
> What is your server.xml config? (please remove comments, passwords etc
> & post it inline, in the response)
>
>
Here it is, nothing special ( except usage of RemoteIpValve ). Thanks for
looking into this problem.
On 14/09/2011 16:38, Darius D. wrote:
>
>> p
>>
>
> Well the problem is that we already looked for that mode of failure, our
> servlet class has 0 instance variables... Basically it is a method like i
> pasted before, doing HttpSession session = request.getSession(); and if
> session is valid (i
Pid * wrote:
>
> On 14/09/2011 11:55, Darius D. wrote:
>
> They are in *that* thread.
>
> It is possible to expose either request or response object outside of
> the scope of the thread, so a second request sees a modified version of
> the same object.
>
> E.g.
>
> public class SomeServlet
On 14/09/2011 11:55, Darius D. wrote:
>
>
>
> Pid * wrote:
>>
>> doProcess(req, res) is not a Servlet API method. What other method(s)
>> call it?
>>
>> Usually this type of thing occurs because the request (or response) is
>> being held as an instance field somewhere in a thread-unsafe way.
>>
Pid * wrote:
>
> doProcess(req, res) is not a Servlet API method. What other method(s)
> call it?
>
> Usually this type of thing occurs because the request (or response) is
> being held as an instance field somewhere in a thread-unsafe way.
>
>
It is called from:
public void doGet(H
On 14/09/2011 08:34, Darius D. wrote:
>
> Hi,
>
> we have a problem of request params beeing null in servlets where it
> shouldn't be ( post or get, in get we can even see that
> request.getQueryString() is fine, but params are null).
>
> It is more pronounced when using dedicated thread executo
Hi,
we have a problem of request params beeing null in servlets where it
shouldn't be ( post or get, in get we can even see that
request.getQueryString() is fine, but params are null).
It is more pronounced when using dedicated thread executor, moving to
threads provided by connector itself (wit
