2:22 a.m.
Memory leak in EJB3.1 no interface view for stateful beans
----------------------------------------------------------
Key: JBAS-9397
URL: https://issues.jboss.org/browse/JBAS-9397
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: All platforms
Reporter: Jürgen Koras
Assignee: Carlo de Wolf
Priority: Critical
Using a stateful no-interface bean causes a memory leak in PermGen space. This can easily
be reproduced by creating and removing such a bean. On my machine it fails after 22500
instances.
The problem is that for each instance of a bean a new Proxy-class is generated.
This is done using javassist framework in the class
org.jboss.ejb3.proxy.javassist.JavassistProxyFactory in method createProxy(Class[],
InvocationHandler). Here the depreciated javassist method (instance).setHandler(...) is
used. Due to documentation
(http://www.csg.is.titech.ac.jp/~chiba/javassist/html/javassist/util/proxy...)
this call deactivates the cache!
The solution is simply to remove that call and pass the handler right in the
(instance).create(...) method.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:24 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-9397) Memory leak in EJB3.1 no interface view for stateful beans
[
https://issues.jboss.org/browse/JBAS-9397?page=com.atlassian.jira.plugin....
]
Jürgen Koras updated JBAS-9397:
-------------------------------
Attachment: JavassistProxyFactory-patch.txt
Patch to solve the issue
Memory leak in EJB3.1 no interface view for stateful beans
----------------------------------------------------------
Key: JBAS-9397
URL: https://issues.jboss.org/browse/JBAS-9397
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: All platforms
Reporter: Jürgen Koras
Assignee: Carlo de Wolf
Priority: Critical
Attachments: JavassistProxyFactory-patch.txt
Using a stateful no-interface bean causes a memory leak in PermGen space. This can easily
be reproduced by creating and removing such a bean. On my machine it fails after 22500
instances.
The problem is that for each instance of a bean a new Proxy-class is generated.
This is done using javassist framework in the class
org.jboss.ejb3.proxy.javassist.JavassistProxyFactory in method createProxy(Class[],
InvocationHandler). Here the depreciated javassist method (instance).setHandler(...) is
used. Due to documentation
(http://www.csg.is.titech.ac.jp/~chiba/javassist/html/javassist/util/proxy...)
this call deactivates the cache!
The solution is simply to remove that call and pass the handler right in the
(instance).create(...) method.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:02 a.m.
New subject: [JBoss JIRA] Assigned: (JBAS-9397) Memory leak in EJB3.1 no interface view for stateful beans
[
https://issues.jboss.org/browse/JBAS-9397?page=com.atlassian.jira.plugin....
]
Carlo de Wolf reassigned JBAS-9397:
-----------------------------------
Assignee: jaikiran pai (was: Carlo de Wolf)
Memory leak in EJB3.1 no interface view for stateful beans
----------------------------------------------------------
Key: JBAS-9397
URL: https://issues.jboss.org/browse/JBAS-9397
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: All platforms
Reporter: Jürgen Koras
Assignee: jaikiran pai
Priority: Critical
Attachments: JavassistProxyFactory-patch.txt
Using a stateful no-interface bean causes a memory leak in PermGen space. This can easily
be reproduced by creating and removing such a bean. On my machine it fails after 22500
instances.
The problem is that for each instance of a bean a new Proxy-class is generated.
This is done using javassist framework in the class
org.jboss.ejb3.proxy.javassist.JavassistProxyFactory in method createProxy(Class[],
InvocationHandler). Here the depreciated javassist method (instance).setHandler(...) is
used. Due to documentation
(http://www.csg.is.titech.ac.jp/~chiba/javassist/html/javassist/util/proxy...)
this call deactivates the cache!
The solution is simply to remove that call and pass the handler right in the
(instance).create(...) method.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:09 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-9397) Memory leak in EJB3.1 no interface view for stateful beans
[
https://issues.jboss.org/browse/JBAS-9397?page=com.atlassian.jira.plugin....
]
jaikiran pai updated JBAS-9397:
-------------------------------
Fix Version/s: 6.1.0
Memory leak in EJB3.1 no interface view for stateful beans
----------------------------------------------------------
Key: JBAS-9397
URL: https://issues.jboss.org/browse/JBAS-9397
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: All platforms
Reporter: Jürgen Koras
Assignee: jaikiran pai
Priority: Critical
Fix For: 6.1.0
Attachments: JavassistProxyFactory-patch.txt
Using a stateful no-interface bean causes a memory leak in PermGen space. This can easily
be reproduced by creating and removing such a bean. On my machine it fails after 22500
instances.
The problem is that for each instance of a bean a new Proxy-class is generated.
This is done using javassist framework in the class
org.jboss.ejb3.proxy.javassist.JavassistProxyFactory in method createProxy(Class[],
InvocationHandler). Here the depreciated javassist method (instance).setHandler(...) is
used. Due to documentation
(http://www.csg.is.titech.ac.jp/~chiba/javassist/html/javassist/util/proxy...)
this call deactivates the cache!
The solution is simply to remove that call and pass the handler right in the
(instance).create(...) method.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:12 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-9397) Memory leak in EJB3.1 no interface view for stateful beans
[
https://issues.jboss.org/browse/JBAS-9397?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on JBAS-9397:
------------------------------------
Jürgen, can you please try the following steps and see if it fixes the issue:
1) Download the latest snapshot containing this fix from here
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
2) Rename the downloaded file to proxy-javassist.jar
3) *Replace* the proxy-javassist.jar from JBOSS_HOME/common/lib with this new one (Take a
backup of the original JBOSS_HOME/common/lib/proxy-javassist.jar if you want to).
4) Test it out.
Let us know how it goes. If it fixes the issue, I'll do a release and integrate it
with 6.1.0 AS.
Memory leak in EJB3.1 no interface view for stateful beans
----------------------------------------------------------
Key: JBAS-9397
URL: https://issues.jboss.org/browse/JBAS-9397
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: All platforms
Reporter: Jürgen Koras
Assignee: jaikiran pai
Priority: Critical
Fix For: 6.1.0
Attachments: JavassistProxyFactory-patch.txt
Using a stateful no-interface bean causes a memory leak in PermGen space. This can easily
be reproduced by creating and removing such a bean. On my machine it fails after 22500
instances.
The problem is that for each instance of a bean a new Proxy-class is generated.
This is done using javassist framework in the class
org.jboss.ejb3.proxy.javassist.JavassistProxyFactory in method createProxy(Class[],
InvocationHandler). Here the depreciated javassist method (instance).setHandler(...) is
used. Due to documentation
(http://www.csg.is.titech.ac.jp/~chiba/javassist/html/javassist/util/proxy...)
this call deactivates the cache!
The solution is simply to remove that call and pass the handler right in the
(instance).create(...) method.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:13 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-9397) Memory leak in EJB3.1 no interface view for stateful beans
[
https://issues.jboss.org/browse/JBAS-9397?page=com.atlassian.jira.plugin....
]
Jürgen Koras commented on JBAS-9397:
------------------------------------
I can confirm that my test case runs well with these changes.
So it fixes the issue. :-)
Memory leak in EJB3.1 no interface view for stateful beans
----------------------------------------------------------
Key: JBAS-9397
URL: https://issues.jboss.org/browse/JBAS-9397
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: All platforms
Reporter: Jürgen Koras
Assignee: jaikiran pai
Priority: Critical
Fix For: 6.1.0
Attachments: JavassistProxyFactory-patch.txt
Using a stateful no-interface bean causes a memory leak in PermGen space. This can easily
be reproduced by creating and removing such a bean. On my machine it fails after 22500
instances.
The problem is that for each instance of a bean a new Proxy-class is generated.
This is done using javassist framework in the class
org.jboss.ejb3.proxy.javassist.JavassistProxyFactory in method createProxy(Class[],
InvocationHandler). Here the depreciated javassist method (instance).setHandler(...) is
used. Due to documentation
(http://www.csg.is.titech.ac.jp/~chiba/javassist/html/javassist/util/proxy...)
this call deactivates the cache!
The solution is simply to remove that call and pass the handler right in the
(instance).create(...) method.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:28 p.m.
New subject: [JBoss JIRA] Resolved: (JBAS-9397) Memory leak in EJB3.1 no interface view for stateful beans
[
https://issues.jboss.org/browse/JBAS-9397?page=com.atlassian.jira.plugin....
]
jaikiran pai resolved JBAS-9397.
--------------------------------
Resolution: Done
Commit r111741 contains a upgrade of EJB3 depchain to 1.0.1 which contains this fix.
Marking this as resolved. The fix will be available in the next nightly build
http://community.jboss.org/thread/161386
Memory leak in EJB3.1 no interface view for stateful beans
----------------------------------------------------------
Key: JBAS-9397
URL: https://issues.jboss.org/browse/JBAS-9397
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB
Affects Versions: 6.0.0.Final
Environment: All platforms
Reporter: Jürgen Koras
Assignee: jaikiran pai
Priority: Critical
Fix For: 6.1.0
Attachments: JavassistProxyFactory-patch.txt
Using a stateful no-interface bean causes a memory leak in PermGen space. This can easily
be reproduced by creating and removing such a bean. On my machine it fails after 22500
instances.
The problem is that for each instance of a bean a new Proxy-class is generated.
This is done using javassist framework in the class
org.jboss.ejb3.proxy.javassist.JavassistProxyFactory in method createProxy(Class[],
InvocationHandler). Here the depreciated javassist method (instance).setHandler(...) is
used. Due to documentation
(http://www.csg.is.titech.ac.jp/~chiba/javassist/html/javassist/util/proxy...)
this call deactivates the cache!
The solution is simply to remove that call and pass the handler right in the
(instance).create(...) method.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4870
days inactive
4911
days old
6 comments
3 participants
participants (3)
-
Carlo de Wolf (JIRA) -
jaikiran pai (JIRA)
-
Jürgen Koras (JIRA)