Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Date: Fri, 6 Jan 2017 22:21:41 +0000 (UTC)
From: modjklist@comcast.net
To: Tomcat Users List <users@tomcat.apache.org>
Message-ID: <990907766.85743791.1483741301112.JavaMail.zimbra@comcast.net>
In-Reply-To: <181794329.85741627.1483741080719.JavaMail.zimbra@comcast.net>
Subject: help resolving memory leak error message
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Thread-Topic: help resolving memory leak error message
Thread-Index: 0Q389wwEXmkEaJ6RjYjN5tdZh38VWw==
archived-at: Fri, 06 Jan 2017 22:21:53 -0000

I'm porting a Apache Flex (with Apache BlazeDS) web app from glassfish to tomcat 8.5.9, and observing the following severe error.  

06-Jan-2017 13:49:07.644 SEVERE [ContainerBackgroundProcessor[StandardEngine[Catalina]]] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [myApp] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@4d6e6d7b]) and a value of type [flex.messaging.io.SerializationContext] (value [flex.messaging.io.SerializationContext@66135428]) 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. 

Is this a warning or an actual error that is causing a memory leak?

Can anyone point me in the right direction to resolve this? I'm a new Tomcat user (please try to be explicit). 

Thanks for any advice/comments.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org