Thanks for the comment, I will search our code and see where we modify the
headers concurrently.
Bertalan Kis
-Original Message-
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
Sent: 03 February 2010 06:34
To: Tomcat Users List
Subject: Re: NullPointerException in MimeHeaders
2010/2/2 Bertalan Kis :
> It seems attachments are disabled.
> Here are the stacktraces:
>
> Jan 29, 2010 1:13:20 AM
> com.sun.xml.ws.transport.http.servlet.WSServletDelegate doGet
> SEVERE: caught throwable
> java.lang.NullPointerException
> at
> org.apache.tomcat.util.http.MimeHeaders.se
[mailto:chuck.caldar...@unisys.com]
Sent: 02 February 2010 13:13
To: Tomcat Users List
Subject: RE: NullPointerException in MimeHeaders
> From: Bertalan Kis [mailto:bertalan@razorfish.com]
> Subject: RE: NullPointerException in MimeHeaders
>
> I can't see any suspicious in that class, maybe y
> From: Bertalan Kis [mailto:bertalan@razorfish.com]
> Subject: RE: NullPointerException in MimeHeaders
>
> I can't see any suspicious in that class, maybe you can:
The fact that the filter /sometimes/ chooses synchronization makes me very
suspicious, especially since the
request.getParameter("xsd") != null;
}
Cheers,
Bertalan Kis
-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: 02 February 2010 12:53
To: Tomcat Users List
Subject: RE: NullPointerException in MimeHeaders
> From: Bertalan Kis [
> From: Bertalan Kis [mailto:bertalan@razorfish.com]
> Subject: RE: NullPointerException in MimeHeaders
>
> com.dnaO2.openspace.client.filter.MetadataRequestSynchFilter.doFilter
> (MetadataRequestSynchFilter.java:54)
The above is the spot you should be looking at, since that&#
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Bertalan Kis
-Original Message-
From: Bertalan Kis
Sent: 02 February 2010 12:25
To: users@tomcat.apache.org
Subject: NullPointerException in MimeHeaders
Hi,
At my
Hi,
At my company we can see NullPointerExceptions in the catalina.out files (see
the attachments). We use Tomcat 6.0.14 on our 4 servers to handle web service
calls from another tier of the application. The errors occur when the soap call
was processed and ready to send the prepared response b
