Hi,
I have profiled the application using JProfiler,and it seems to me that its my
servlet which is taking the majority of time.
Though the time is in mili seconds,but I guess since the servlet is code is
same as with Tomcat 6.0.18 is it the Servlet 3.0 API which is causing the
reduced throu
Hi Jesse
you can configure your customised Jaxb factory implementor by implementing a
jaxb.properties file
with a javax.xml.bind.context.factory=value
javax.xml.bind.context.factory=org.eclipse.persistence.jaxb.JAXBContextFactory
be aware with key=value value is the name of the class that imple
Greetings,
I am using Apache Tomcat 7.0.40, via IBM Java 7 SR2. I am seeing the
following on Tomcat shutdown:
org.apache.catalina.loader.WebappClassLoader.checkThreadLocalMapForLeaks
The web application [] created a ThreadLocal with key of type
[com.sun.xml.bind.v2.runtime.Coordinator$1] (value
[
On May 19, 2013, at 10:01 AM, Caldarale, Charles R wrote:
>> From: Nick Williams [mailto:nicho...@nicholaswilliams.net]
>> Subject: Re: LOG4J2-223: IllegalStateException thrown during Tomcat shutdown
>> (memory leak, it looks like)
>
>> Log4j 1 never required a listener to be configured to be
> From: Nick Williams [mailto:nicho...@nicholaswilliams.net]
> Subject: Re: LOG4J2-223: IllegalStateException thrown during Tomcat shutdown
> (memory leak, it looks like)
> Log4j 1 never required a listener to be configured to be shut down
> properly when an application is undeployed.
What bea
On May 19, 2013, at 3:33 AM, Mark Thomas wrote:
> On 19/05/2013 05:57, Nick Williams wrote:
>> Can one of the very knowledgeable developers that have been
>> discussing memory leaks in the last few days (re: Possible
>> false-postive with JreMemoryLeakPreventionListener and Tomcat's JDBC
>> Pool
On 19/05/2013 05:57, Nick Williams wrote:
> Can one of the very knowledgeable developers that have been
> discussing memory leaks in the last few days (re: Possible
> false-postive with JreMemoryLeakPreventionListener and Tomcat's JDBC
> Pool and OracleTimeoutPollingThread) chime in on this Log4j 2