7:10 p.m.
Philippe Guinot created AS7-3733:
------------------------------------
Summary: AWT AppContext / EventQueue ClassLoader Memory Leaks
Key: AS7-3733
URL: https://issues.jboss.org/browse/AS7-3733
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Environment: AS 7 running on JDK 1.6.0_30, Windows 7
Reporter: Philippe Guinot
Assignee: Remy Maucherat
The use of libraries using awt components creates ClassLoader Memory Leaks. This is
because the first call to the sun AppContext class makes a static reference to the current
class loader.
Same thing goes with the creation of the AWT Event Queue, as an example the use of the
class java.awt.Color makes a static init call to java.awt.Toolkit which creates an AWT
EventQueue despite the headless mode. The EventQueue also keep a reference to the current
context with the class loader.
The current work around I've found is to add a call to:
{code}java.awt.Toolkit.getDefaultToolkit();{code}
before the application gets loaded.
This causes the EventQueue to be created and the AppContext to be initialized.
Then, as the AWT static references are final, I get rid of this issue for the rest of the
server lifecycle.
I put this code in org.jboss.as.server.Main, just after line 91. However a proper solution
would be to use org.apache.catalina.core.JreMemoryLeakPreventionListener which is present
in the JBoss Web jar but not used... (cf. https://community.jboss.org/thread/164760 )
However the Tomcat code deals only with the AppContext, not the EventQueue!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:34 p.m.
[
https://issues.jboss.org/browse/AS7-3733?page=com.atlassian.jira.plugin.s...
]
Remy Maucherat resolved AS7-3733.
---------------------------------
Resolution: Duplicate Issue
AS7-3732: Although the issue causing the leak is different, the method to work around it
should be the same, webapps in JBoss AS can use a listener like Tomcat does.
AWT AppContext / EventQueue ClassLoader Memory Leaks
----------------------------------------------------
Key: AS7-3733
URL: https://issues.jboss.org/browse/AS7-3733
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Environment: AS 7 running on JDK 1.6.0_30, Windows 7
Reporter: Philippe Guinot
Assignee: Remy Maucherat
Labels: appcontext, as7, awt, classloader, eventqueue, jboss, leak
The use of libraries using awt components creates ClassLoader Memory Leaks. This is
because the first call to the sun AppContext class makes a static reference to the current
class loader.
Same thing goes with the creation of the AWT Event Queue, as an example the use of the
class java.awt.Color makes a static init call to java.awt.Toolkit which creates an AWT
EventQueue despite the headless mode. The EventQueue also keep a reference to the current
context with the class loader.
The current work around I've found is to add a call to:
{code}java.awt.Toolkit.getDefaultToolkit();{code}
before the application gets loaded.
This causes the EventQueue to be created and the AppContext to be initialized.
Then, as the AWT static references are final, I get rid of this issue for the rest of the
server lifecycle.
I put this code in org.jboss.as.server.Main, just after line 91. However a proper
solution would be to use org.apache.catalina.core.JreMemoryLeakPreventionListener which is
present in the JBoss Web jar but not used... (cf.
https://community.jboss.org/thread/164760 ) However the Tomcat code deals only with the
AppContext, not the EventQueue!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:42 p.m.
[
https://issues.jboss.org/browse/AS7-3733?page=com.atlassian.jira.plugin.s...
]
Philippe Guinot updated AS7-3733:
---------------------------------
Forum Reference: https://community.jboss.org/thread/195134
AWT AppContext / EventQueue ClassLoader Memory Leaks
----------------------------------------------------
Key: AS7-3733
URL: https://issues.jboss.org/browse/AS7-3733
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Environment: AS 7 running on JDK 1.6.0_30, Windows 7
Reporter: Philippe Guinot
Assignee: Remy Maucherat
Labels: appcontext, as7, awt, classloader, eventqueue, jboss, leak
The use of libraries using awt components creates ClassLoader Memory Leaks. This is
because the first call to the sun AppContext class makes a static reference to the current
class loader.
Same thing goes with the creation of the AWT Event Queue, as an example the use of the
class java.awt.Color makes a static init call to java.awt.Toolkit which creates an AWT
EventQueue despite the headless mode. The EventQueue also keep a reference to the current
context with the class loader.
The current work around I've found is to add a call to:
{code}java.awt.Toolkit.getDefaultToolkit();{code}
before the application gets loaded.
This causes the EventQueue to be created and the AppContext to be initialized.
Then, as the AWT static references are final, I get rid of this issue for the rest of the
server lifecycle.
I put this code in org.jboss.as.server.Main, just after line 91. However a proper
solution would be to use org.apache.catalina.core.JreMemoryLeakPreventionListener which is
present in the JBoss Web jar but not used... (cf.
https://community.jboss.org/thread/164760 ) However the Tomcat code deals only with the
AppContext, not the EventQueue!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:46 p.m.
[
https://issues.jboss.org/browse/AS7-3733?page=com.atlassian.jira.plugin.s...
]
Philippe Guinot commented on AS7-3733:
--------------------------------------
How do I use a listener so ?
And how I can be sure that the context class loader won't be the application's
class loader when running the code of that listener?
AWT AppContext / EventQueue ClassLoader Memory Leaks
----------------------------------------------------
Key: AS7-3733
URL: https://issues.jboss.org/browse/AS7-3733
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Environment: AS 7 running on JDK 1.6.0_30, Windows 7
Reporter: Philippe Guinot
Assignee: Remy Maucherat
Labels: appcontext, as7, awt, classloader, eventqueue, jboss, leak
The use of libraries using awt components creates ClassLoader Memory Leaks. This is
because the first call to the sun AppContext class makes a static reference to the current
class loader.
Same thing goes with the creation of the AWT Event Queue, as an example the use of the
class java.awt.Color makes a static init call to java.awt.Toolkit which creates an AWT
EventQueue despite the headless mode. The EventQueue also keep a reference to the current
context with the class loader.
The current work around I've found is to add a call to:
{code}java.awt.Toolkit.getDefaultToolkit();{code}
before the application gets loaded.
This causes the EventQueue to be created and the AppContext to be initialized.
Then, as the AWT static references are final, I get rid of this issue for the rest of the
server lifecycle.
I put this code in org.jboss.as.server.Main, just after line 91. However a proper
solution would be to use org.apache.catalina.core.JreMemoryLeakPreventionListener which is
present in the JBoss Web jar but not used... (cf.
https://community.jboss.org/thread/164760 ) However the Tomcat code deals only with the
AppContext, not the EventQueue!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:51 p.m.
[
https://issues.jboss.org/browse/AS7-3733?page=com.atlassian.jira.plugin.s...
]
Philippe Guinot edited comment on AS7-3733 at 2/13/12 9:19 AM:
---------------------------------------------------------------
How do I use a listener so ?
And how I can be sure that the context class loader won't be the application's
class loader when running the code of that listener?
If I define a webapp listener, the current context will refer to the application's
class loader and so the fix won't work.
This patch need to be run outside the webapp...
was (Author: guinotphil):
How do I use a listener so ?
And how I can be sure that the context class loader won't be the application's
class loader when running the code of that listener?
AWT AppContext / EventQueue ClassLoader Memory Leaks
----------------------------------------------------
Key: AS7-3733
URL: https://issues.jboss.org/browse/AS7-3733
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Environment: AS 7 running on JDK 1.6.0_30, Windows 7
Reporter: Philippe Guinot
Assignee: Remy Maucherat
Labels: appcontext, as7, awt, classloader, eventqueue, jboss, leak
The use of libraries using awt components creates ClassLoader Memory Leaks. This is
because the first call to the sun AppContext class makes a static reference to the current
class loader.
Same thing goes with the creation of the AWT Event Queue, as an example the use of the
class java.awt.Color makes a static init call to java.awt.Toolkit which creates an AWT
EventQueue despite the headless mode. The EventQueue also keep a reference to the current
context with the class loader.
The current work around I've found is to add a call to:
{code}java.awt.Toolkit.getDefaultToolkit();{code}
before the application gets loaded.
This causes the EventQueue to be created and the AppContext to be initialized.
Then, as the AWT static references are final, I get rid of this issue for the rest of the
server lifecycle.
I put this code in org.jboss.as.server.Main, just after line 91. However a proper
solution would be to use org.apache.catalina.core.JreMemoryLeakPreventionListener which is
present in the JBoss Web jar but not used... (cf.
https://community.jboss.org/thread/164760 ) However the Tomcat code deals only with the
AppContext, not the EventQueue!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:53 p.m.
[
https://issues.jboss.org/browse/AS7-3733?page=com.atlassian.jira.plugin.s...
]
Philippe Guinot edited comment on AS7-3733 at 2/13/12 9:21 AM:
---------------------------------------------------------------
No it isn't.
If I define a webapp listener, the current context will refer to the application's
class loader and so the fix won't work.
This patch need to be run outside the webapp...
was (Author: guinotphil):
How do I use a listener so ?
And how I can be sure that the context class loader won't be the application's
class loader when running the code of that listener?
If I define a webapp listener, the current context will refer to the application's
class loader and so the fix won't work.
This patch need to be run outside the webapp...
AWT AppContext / EventQueue ClassLoader Memory Leaks
----------------------------------------------------
Key: AS7-3733
URL: https://issues.jboss.org/browse/AS7-3733
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Environment: AS 7 running on JDK 1.6.0_30, Windows 7
Reporter: Philippe Guinot
Assignee: Remy Maucherat
Labels: appcontext, as7, awt, classloader, eventqueue, jboss, leak
The use of libraries using awt components creates ClassLoader Memory Leaks. This is
because the first call to the sun AppContext class makes a static reference to the current
class loader.
Same thing goes with the creation of the AWT Event Queue, as an example the use of the
class java.awt.Color makes a static init call to java.awt.Toolkit which creates an AWT
EventQueue despite the headless mode. The EventQueue also keep a reference to the current
context with the class loader.
The current work around I've found is to add a call to:
{code}java.awt.Toolkit.getDefaultToolkit();{code}
before the application gets loaded.
This causes the EventQueue to be created and the AppContext to be initialized.
Then, as the AWT static references are final, I get rid of this issue for the rest of the
server lifecycle.
I put this code in org.jboss.as.server.Main, just after line 91. However a proper
solution would be to use org.apache.catalina.core.JreMemoryLeakPreventionListener which is
present in the JBoss Web jar but not used... (cf.
https://community.jboss.org/thread/164760 ) However the Tomcat code deals only with the
AppContext, not the EventQueue!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:05 p.m.
[
https://issues.jboss.org/browse/AS7-3733?page=com.atlassian.jira.plugin.s...
]
Remy Maucherat commented on AS7-3733:
-------------------------------------
jboss-web.xml has container listener configuration, using the listener element and
listener-type sub element with value "LIFECYCLE". This jira is not about web at
all, anyway.
AWT AppContext / EventQueue ClassLoader Memory Leaks
----------------------------------------------------
Key: AS7-3733
URL: https://issues.jboss.org/browse/AS7-3733
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Environment: AS 7 running on JDK 1.6.0_30, Windows 7
Reporter: Philippe Guinot
Assignee: Remy Maucherat
Labels: appcontext, as7, awt, classloader, eventqueue, jboss, leak
The use of libraries using awt components creates ClassLoader Memory Leaks. This is
because the first call to the sun AppContext class makes a static reference to the current
class loader.
Same thing goes with the creation of the AWT Event Queue, as an example the use of the
class java.awt.Color makes a static init call to java.awt.Toolkit which creates an AWT
EventQueue despite the headless mode. The EventQueue also keep a reference to the current
context with the class loader.
The current work around I've found is to add a call to:
{code}java.awt.Toolkit.getDefaultToolkit();{code}
before the application gets loaded.
This causes the EventQueue to be created and the AppContext to be initialized.
Then, as the AWT static references are final, I get rid of this issue for the rest of the
server lifecycle.
I put this code in org.jboss.as.server.Main, just after line 91. However a proper
solution would be to use org.apache.catalina.core.JreMemoryLeakPreventionListener which is
present in the JBoss Web jar but not used... (cf.
https://community.jboss.org/thread/164760 ) However the Tomcat code deals only with the
AppContext, not the EventQueue!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:02 p.m.
[
https://issues.jboss.org/browse/AS7-3733?page=com.atlassian.jira.plugin.s...
]
Philippe Guinot commented on AS7-3733:
--------------------------------------
Remy,
Using a listener is not a good solution, I'm afraid. Because at that point the current
context class loader is the application class loader.
When the AWT Thread is created it refers so to the application's CL, hence the leak.
So this is a code that must be called outside any application specific code. Maybe not the
Web component if you want.. Feel free to re-affect this JIRA to anyone, but it should be
reopened as long as the given workaround you suggested does not work.
PS: using Thread.currentThread().setContextClassLoader(...) before creating a thread, does
not prevent the child thread keeping a reference to the parent thread's CL. I wish it
could, but it would be to easy.. A reference to the class loader is also kept in the
inheritedAccessControlerContext.
AWT AppContext / EventQueue ClassLoader Memory Leaks
----------------------------------------------------
Key: AS7-3733
URL: https://issues.jboss.org/browse/AS7-3733
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Environment: AS 7 running on JDK 1.6.0_30, Windows 7
Reporter: Philippe Guinot
Assignee: Remy Maucherat
Labels: appcontext, as7, awt, classloader, eventqueue, jboss, leak
The use of libraries using awt components creates ClassLoader Memory Leaks. This is
because the first call to the sun AppContext class makes a static reference to the current
class loader.
Same thing goes with the creation of the AWT Event Queue, as an example the use of the
class java.awt.Color makes a static init call to java.awt.Toolkit which creates an AWT
EventQueue despite the headless mode. The EventQueue also keep a reference to the current
context with the class loader.
The current work around I've found is to add a call to:
{code}java.awt.Toolkit.getDefaultToolkit();{code}
before the application gets loaded.
This causes the EventQueue to be created and the AppContext to be initialized.
Then, as the AWT static references are final, I get rid of this issue for the rest of the
server lifecycle.
I put this code in org.jboss.as.server.Main, just after line 91. However a proper
solution would be to use org.apache.catalina.core.JreMemoryLeakPreventionListener which is
present in the JBoss Web jar but not used... (cf.
https://community.jboss.org/thread/164760 ) However the Tomcat code deals only with the
AppContext, not the EventQueue!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:26 p.m.
[
https://issues.jboss.org/browse/AS7-3733?page=com.atlassian.jira.plugin.s...
]
Remy Maucherat commented on AS7-3733:
-------------------------------------
The context classloader is not yet bound during the init event, which is the one used by
the Tomcat listener. I did sync with the Tomcat listener to have it at hand for people
willing to hack, but it won't do the exact same thing since deployment is not the same
[you can add your own "memoryleak" subsystem to cleanly replicate what Tomcat is
doing if you really need it].
It is up to the application server to add these leaks hacking though, and it doesn't
seem to be something that will happen.
AWT AppContext / EventQueue ClassLoader Memory Leaks
----------------------------------------------------
Key: AS7-3733
URL: https://issues.jboss.org/browse/AS7-3733
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Environment: AS 7 running on JDK 1.6.0_30, Windows 7
Reporter: Philippe Guinot
Assignee: Remy Maucherat
Labels: appcontext, as7, awt, classloader, eventqueue, jboss, leak
The use of libraries using awt components creates ClassLoader Memory Leaks. This is
because the first call to the sun AppContext class makes a static reference to the current
class loader.
Same thing goes with the creation of the AWT Event Queue, as an example the use of the
class java.awt.Color makes a static init call to java.awt.Toolkit which creates an AWT
EventQueue despite the headless mode. The EventQueue also keep a reference to the current
context with the class loader.
The current work around I've found is to add a call to:
{code}java.awt.Toolkit.getDefaultToolkit();{code}
before the application gets loaded.
This causes the EventQueue to be created and the AppContext to be initialized.
Then, as the AWT static references are final, I get rid of this issue for the rest of the
server lifecycle.
I put this code in org.jboss.as.server.Main, just after line 91. However a proper
solution would be to use org.apache.catalina.core.JreMemoryLeakPreventionListener which is
present in the JBoss Web jar but not used... (cf.
https://community.jboss.org/thread/164760 ) However the Tomcat code deals only with the
AppContext, not the EventQueue!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:46 p.m.
[
https://issues.jboss.org/browse/AS7-3733?page=com.atlassian.jira.plugin.s...
]
Philippe Guinot commented on AS7-3733:
--------------------------------------
Thank you.
I don't mind creating my own listener after all, because I may need to init other
things at startup.
However, with this listener added in jboss-web.xml
<listener>
<class-name>mypackage.MemoryLeakPreventionListener</class-name>
<listener-type>LIFECYCLE</listener-type>
</listener>
It is actually called only since the 'after-deploy' event. Maybe I haven't
declared it in the right place... Where is that jboss-web.xml supposed to be ?
AWT AppContext / EventQueue ClassLoader Memory Leaks
----------------------------------------------------
Key: AS7-3733
URL: https://issues.jboss.org/browse/AS7-3733
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Environment: AS 7 running on JDK 1.6.0_30, Windows 7
Reporter: Philippe Guinot
Assignee: Remy Maucherat
Labels: appcontext, as7, awt, classloader, eventqueue, jboss, leak
The use of libraries using awt components creates ClassLoader Memory Leaks. This is
because the first call to the sun AppContext class makes a static reference to the current
class loader.
Same thing goes with the creation of the AWT Event Queue, as an example the use of the
class java.awt.Color makes a static init call to java.awt.Toolkit which creates an AWT
EventQueue despite the headless mode. The EventQueue also keep a reference to the current
context with the class loader.
The current work around I've found is to add a call to:
{code}java.awt.Toolkit.getDefaultToolkit();{code}
before the application gets loaded.
This causes the EventQueue to be created and the AppContext to be initialized.
Then, as the AWT static references are final, I get rid of this issue for the rest of the
server lifecycle.
I put this code in org.jboss.as.server.Main, just after line 91. However a proper
solution would be to use org.apache.catalina.core.JreMemoryLeakPreventionListener which is
present in the JBoss Web jar but not used... (cf.
https://community.jboss.org/thread/164760 ) However the Tomcat code deals only with the
AppContext, not the EventQueue!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:02 p.m.
[
https://issues.jboss.org/browse/AS7-3733?page=com.atlassian.jira.plugin.s...
]
Remy Maucherat commented on AS7-3733:
-------------------------------------
Ok, they get added, but too late. It won't work unless I add the configured listeners
a little bit earlier, which is possible.
AWT AppContext / EventQueue ClassLoader Memory Leaks
----------------------------------------------------
Key: AS7-3733
URL: https://issues.jboss.org/browse/AS7-3733
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Environment: AS 7 running on JDK 1.6.0_30, Windows 7
Reporter: Philippe Guinot
Assignee: Remy Maucherat
Labels: appcontext, as7, awt, classloader, eventqueue, jboss, leak
The use of libraries using awt components creates ClassLoader Memory Leaks. This is
because the first call to the sun AppContext class makes a static reference to the current
class loader.
Same thing goes with the creation of the AWT Event Queue, as an example the use of the
class java.awt.Color makes a static init call to java.awt.Toolkit which creates an AWT
EventQueue despite the headless mode. The EventQueue also keep a reference to the current
context with the class loader.
The current work around I've found is to add a call to:
{code}java.awt.Toolkit.getDefaultToolkit();{code}
before the application gets loaded.
This causes the EventQueue to be created and the AppContext to be initialized.
Then, as the AWT static references are final, I get rid of this issue for the rest of the
server lifecycle.
I put this code in org.jboss.as.server.Main, just after line 91. However a proper
solution would be to use org.apache.catalina.core.JreMemoryLeakPreventionListener which is
present in the JBoss Web jar but not used... (cf.
https://community.jboss.org/thread/164760 ) However the Tomcat code deals only with the
AppContext, not the EventQueue!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:46 a.m.
[
https://issues.jboss.org/browse/AS7-3733?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry reopened AS7-3733:
-----------------------------------
AWT AppContext / EventQueue ClassLoader Memory Leaks
----------------------------------------------------
Key: AS7-3733
URL: https://issues.jboss.org/browse/AS7-3733
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Environment: AS 7 running on JDK 1.6.0_30, Windows 7
Reporter: Philippe Guinot
Assignee: Remy Maucherat
Labels: appcontext, as7, awt, classloader, eventqueue, jboss, leak
The use of libraries using awt components creates ClassLoader Memory Leaks. This is
because the first call to the sun AppContext class makes a static reference to the current
class loader.
Same thing goes with the creation of the AWT Event Queue, as an example the use of the
class java.awt.Color makes a static init call to java.awt.Toolkit which creates an AWT
EventQueue despite the headless mode. The EventQueue also keep a reference to the current
context with the class loader.
The current work around I've found is to add a call to:
{code}java.awt.Toolkit.getDefaultToolkit();{code}
before the application gets loaded.
This causes the EventQueue to be created and the AppContext to be initialized.
Then, as the AWT static references are final, I get rid of this issue for the rest of the
server lifecycle.
I put this code in org.jboss.as.server.Main, just after line 91. However a proper
solution would be to use org.apache.catalina.core.JreMemoryLeakPreventionListener which is
present in the JBoss Web jar but not used... (cf.
https://community.jboss.org/thread/164760 ) However the Tomcat code deals only with the
AppContext, not the EventQueue!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:46 a.m.
[
https://issues.jboss.org/browse/AS7-3733?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry resolved AS7-3733.
-----------------------------------
Fix Version/s: 7.1.1.Final
Resolution: Done
AWT AppContext / EventQueue ClassLoader Memory Leaks
----------------------------------------------------
Key: AS7-3733
URL: https://issues.jboss.org/browse/AS7-3733
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Environment: AS 7 running on JDK 1.6.0_30, Windows 7
Reporter: Philippe Guinot
Assignee: Remy Maucherat
Labels: appcontext, as7, awt, classloader, eventqueue, jboss, leak
Fix For: 7.1.1.Final
The use of libraries using awt components creates ClassLoader Memory Leaks. This is
because the first call to the sun AppContext class makes a static reference to the current
class loader.
Same thing goes with the creation of the AWT Event Queue, as an example the use of the
class java.awt.Color makes a static init call to java.awt.Toolkit which creates an AWT
EventQueue despite the headless mode. The EventQueue also keep a reference to the current
context with the class loader.
The current work around I've found is to add a call to:
{code}java.awt.Toolkit.getDefaultToolkit();{code}
before the application gets loaded.
This causes the EventQueue to be created and the AppContext to be initialized.
Then, as the AWT static references are final, I get rid of this issue for the rest of the
server lifecycle.
I put this code in org.jboss.as.server.Main, just after line 91. However a proper
solution would be to use org.apache.catalina.core.JreMemoryLeakPreventionListener which is
present in the JBoss Web jar but not used... (cf.
https://community.jboss.org/thread/164760 ) However the Tomcat code deals only with the
AppContext, not the EventQueue!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:31 p.m.
[
https://issues.jboss.org/browse/AS7-3733?page=com.atlassian.jira.plugin.s...
]
Remy Maucherat commented on AS7-3733:
-------------------------------------
The lifecycle listeners should now get all the events, including init and before_start.
AWT AppContext / EventQueue ClassLoader Memory Leaks
----------------------------------------------------
Key: AS7-3733
URL: https://issues.jboss.org/browse/AS7-3733
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Environment: AS 7 running on JDK 1.6.0_30, Windows 7
Reporter: Philippe Guinot
Assignee: Remy Maucherat
Labels: appcontext, as7, awt, classloader, eventqueue, jboss, leak
Fix For: 7.1.1.Final
The use of libraries using awt components creates ClassLoader Memory Leaks. This is
because the first call to the sun AppContext class makes a static reference to the current
class loader.
Same thing goes with the creation of the AWT Event Queue, as an example the use of the
class java.awt.Color makes a static init call to java.awt.Toolkit which creates an AWT
EventQueue despite the headless mode. The EventQueue also keep a reference to the current
context with the class loader.
The current work around I've found is to add a call to:
{code}java.awt.Toolkit.getDefaultToolkit();{code}
before the application gets loaded.
This causes the EventQueue to be created and the AppContext to be initialized.
Then, as the AWT static references are final, I get rid of this issue for the rest of the
server lifecycle.
I put this code in org.jboss.as.server.Main, just after line 91. However a proper
solution would be to use org.apache.catalina.core.JreMemoryLeakPreventionListener which is
present in the JBoss Web jar but not used... (cf.
https://community.jboss.org/thread/164760 ) However the Tomcat code deals only with the
AppContext, not the EventQueue!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4617
days inactive
4621
days old
13 comments
3 participants
participants (3)
-
Brian Stansberry (JIRA) -
Philippe Guinot (JIRA)
-
Remy Maucherat (JIRA)