Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4E4D6469.5090500@christopherschultz.net>
Date: Thu, 18 Aug 2011 15:13:45 -0400
From: Christopher Schultz <chris@christopherschultz.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
 rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: How to handle the AWT-Windows thread?
References: 
 <CAKGC1nhhLEpQQc-ZqSLqC7zLqW1pZ4TA3K0QeevTd7mMBqtovA@mail.gmail.com>
 <4E4D57B6.5090008@apache.org>
 <CAKGC1njbwSWdtfMj8XRj=Fyu_LZCWunnd6d8H2ETg4Ltx61Ucg@mail.gmail.com>
In-Reply-To: 
 <CAKGC1njbwSWdtfMj8XRj=Fyu_LZCWunnd6d8H2ETg4Ltx61Ucg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dan,

On 8/18/2011 2:38 PM, Dan Armbrust wrote:
> On the plus side, since they never actually remove anything they 
> deprecate... maybe I can just "stop" the thread.  Hmm.

The JVM should not launch more than one AWT thread, so you should be
okay. The only issue would be whether or not it inherits the webapp's
context ClassLoader which would really represent a memory leak if you
do live webapp reloads (or undeploy/redeploy).

You would only get this message if the WebappClassLoader was being
used as the ContextClassLoader for this thread, so that must be the case.

You should be able to trick the AWT thread to start using the system
class loader in a ServletContextListener that looks something like this:

init() {

  Thread myThread = Thread.currentThread();
  ClassLoader ccl = myThread.getContextClassLoader(); // PUSH
  myThread.setContextClassLoader(ClassLoader.getSystemClassLoader());

  // do something that triggers the creation of the AWT -- maybe
  // something like "new java.awt.Frame()"

  myThread.setContextClassLoader(ccl); // POP
}

This will pin the system ClassLoader into memory (big deal) instead of
your webapp's. This should fix this particular leak and, by extension,
remove the error message from your logs.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5NZGkACgkQ9CaO5/Lv0PB6bgCgptx6nHRmbobmlscvujuzaNrL
XAoAnRedjsOD0bPuF9Rv/N1c+4g4w+4p
=rJYz
-----END PGP SIGNATURE-----

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