On 23/02/2010 07:33, chinmaytotekar wrote:
Ya got the problem..
The problem was response.getWriter() object was declared as global in
servlet, so it became common to all threads. and if one thread closes it, it
used to give NullPtrException in other threads.
Every time, a coconut.
p
Kons
Ya got the problem..
The problem was response.getWriter() object was declared as global in
servlet, so it became common to all threads. and if one thread closes it, it
used to give NullPtrException in other threads.
Konstantin Kolinko wrote:
>
> 2010/2/19 Christopher Schultz :
>> Konstantin,
2010/2/19 Christopher Schultz :
> Konstantin,
>
> On 2/19/2010 2:22 PM, Konstantin Kolinko wrote:
>> 1. The OP (chinmaytotekar) never mentioned what Tomcat version (s)he was
>> using.
>> What a disgrace.
>
> The thread subject seems to contradict this statement.
>
Ah, sorry. I missed that.
Best
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Konstantin,
On 2/19/2010 2:22 PM, Konstantin Kolinko wrote:
> 1. The OP (chinmaytotekar) never mentioned what Tomcat version (s)he was
> using.
> What a disgrace.
The thread subject seems to contradict this statement.
> 2. For example of similar st
2010/2/19 Pid :
> On 19/02/2010 16:49, Christopher Schultz wrote:
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Pid,
>>
>> On 2/19/2010 11:39 AM, Pid wrote:
>>>
>>> !ThreadSafe
>>>
>>> This type of error was a symptom of the request/response being held as
>>> an instance field in at
On 19/02/2010 16:49, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
On 2/19/2010 11:39 AM, Pid wrote:
!ThreadSafe
This type of error was a symptom of the request/response being held as
an instance field in at least the last one of the couple of recent times
we s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
On 2/19/2010 11:39 AM, Pid wrote:
> !ThreadSafe
>
> This type of error was a symptom of the request/response being held as
> an instance field in at least the last one of the couple of recent times
> we saw this AFAICR.
I certainly agree that t
On 19/02/2010 16:31, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chinmay,
I checked the source, and this is what we've got:
public MessageBytes setValue( String name ) {
for ( int i = 0; i< count; i++ ) {
if(headers[i].getName().equalsIg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chinmay,
I checked the source, and this is what we've got:
public MessageBytes setValue( String name ) {
for ( int i = 0; i < count; i++ ) {
if(headers[i].getName().equalsIgnoreCase(name)) { // 267
for ( int j=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chinmay,
On 2/19/2010 10:50 AM, Christopher Schultz wrote:
> Are you setting any headers in your app? Perhaps one of them is NULL.
I just checked, and this JSP does not trigger an error in TC 6.0.20:
- ---
http:/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chinmay,
On 2/19/2010 7:54 AM, chinmaytotekar wrote:
> I have a servlet and when i call reponse.getWriter().flushBuffer() OR
> reponse.getWriter().println("SOME TEXT"), sometimes it gives following types
> of errors. This error does not occur always b
On 19/02/2010 12:54, chinmaytotekar wrote:
Hi
I have a servlet and when i call reponse.getWriter().flushBuffer() OR
reponse.getWriter().println("SOME TEXT"), sometimes it gives following types
of errors. This error does not occur always but sometimes. What can be the
reason for this?
Last tim
12 matches
Mail list logo
