Skip to Main Content

Java EE (Java Enterprise Edition) General Discussion

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

The web application created a ThreadLocal but failed to remove it

nantucketMar 25 2011 — edited Mar 30 2011
Mac OS X 10.5.8
Eclipse Helios
Java 1.6
Tomcat 7.0.11

I'm testing my web application in Eclipse running Tomcat. My web application makes use of JAXB. I'm seeing the following being generated in the console when I shut the server down.

Mar 25, 2011 2:01:27 PM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks
SEVERE: The web application [foo] created a ThreadLocal with key of type [com.sun.xml.bind.v2.runtime.Coordinator$1] (value [com.sun.xml.bind.v2.runtime.Coordinator$1@4f50f0e2]) and a value of type [com.sun.xml.bind.v2.runtime.Coordinator[]] (value [[Lcom.sun.xml.bind.v2.runtime.Coordinator;@4af6ae1c]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.

I'd appreciate any feedback from anyone who has any experience with these sorts of messages or has ideas about how I might resolve this.
I'm seeing other messages as well which refer to my own classes in relation to the work I've done with JAXB. But how do I close out or eliminate these ThreadLocals? Is it safe to let Tomcat manage them by renewing them?

Thanks.
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Apr 27 2011
Added on Mar 25 2011
1 comment
3,574 views