-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
On 8/21/2011 4:53 AM, Pid wrote:
On 21/08/2011 01:19, Christopher Schultz wrote:
I'm not sure how one would intercept the call, though. I've
never looked into it, but I would guess that
Toolkit.getDefaultToolkit can be configured to return
On 21/08/2011 01:19, Christopher Schultz wrote:
Pid,
On 8/20/2011 6:06 PM, Pid wrote:
On 19/08/2011 15:45, Christopher Schultz wrote:
Dan,
On 8/18/2011 5:22 PM, Dan Armbrust wrote:
Toolkit.getDefaultToolkit().createImage(new byte[]{});
Simply calling getDefaultToolkit will do the trick:
On 19/08/2011 15:45, Christopher Schultz wrote:
Dan,
On 8/18/2011 5:22 PM, Dan Armbrust wrote:
Toolkit.getDefaultToolkit().createImage(new byte[]{});
Simply calling getDefaultToolkit will do the trick: you don't have to
waste time creating an image.
I'll implement this in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
On 8/20/2011 6:06 PM, Pid wrote:
On 19/08/2011 15:45, Christopher Schultz wrote:
Dan,
On 8/18/2011 5:22 PM, Dan Armbrust wrote:
Toolkit.getDefaultToolkit().createImage(new byte[]{});
Simply calling getDefaultToolkit will do the trick:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
On 8/18/2011 6:05 PM, Pid wrote:
On 18/08/2011 22:22, Dan Armbrust wrote:
Toolkit.getDefaultToolkit().createImage(new byte[]{});
which avoids Headless issues, but still kicks off the
AWT-Windows thread.
And since it is no longer tied to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan,
On 8/18/2011 5:22 PM, Dan Armbrust wrote:
Toolkit.getDefaultToolkit().createImage(new byte[]{});
Simply calling getDefaultToolkit will do the trick: you don't have to
waste time creating an image.
I'll implement this in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan and Pid,
On 8/18/2011 6:05 PM, Pid wrote:
On 18/08/2011 22:22, Dan Armbrust wrote:
Toolkit.getDefaultToolkit().createImage(new byte[]{});
which avoids Headless issues, but still kicks off the
AWT-Windows thread.
Doesn't the leak
So, yesterday, I finally start working on upgrading on old application
set to a current 6 release of Tomcat.
(Sigh, behind the truck already, seeing the announcement of the next
version today bad timing by me... beside the point)
Some of my web applications are using JFreeChart to generate
On 18/08/2011 19:03, Dan Armbrust wrote:
So, yesterday, I finally start working on upgrading on old application
set to a current 6 release of Tomcat.
(Sigh, behind the truck already, seeing the announcement of the next
version today bad timing by me... beside the point)
Some of my web
(If I can't figure out how to
fix all my issues) I can't ship code to the customers that logs
SEVERE errors on shutdown.
All the leaks should be fixable / possible to workaround.
Mark
If I could update all of my dependencies... I'm guessing many would
just go away. Unfortunately, I'm
-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
On Thu, Aug 18, 2011 at 2:13 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
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
On 18/08/2011 22:22, Dan Armbrust wrote:
On Thu, Aug 18, 2011 at 2:13 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
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
13 matches
Mail list logo
