[jboss-jira] [JBoss JIRA] Updated: (JBAS-3428) org.jboss.ejb.SecurityActions.getMBeanProxy duplicating proxies

[Clebert Suconic (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-3428?page=all ]

Clebert Suconic updated JBAS-3428:
----------------------------------

    Description: 
Due to JBAS-3013 we changed SecurityActions to use MBeanProxyExt.create what is creating a fake ClassLoader on every call what is forcing Proxy.newInstance to create a new proxy. (Since ClassLoader is a key parameter to a proxy creation).
This causes excessive GC, memory leaks in production and server outage when using EJB (2.0) or anything related to org.jboss.ejb.Container




  was:
Due to JBAS-3013 we change SecurityActions to use MBeanProxyExt.create what is creating a fake ClassLoader on every call what is focring Proxy.newInstance to create a new proxy. (Since ClassLoader is a key parameter to a proxy creation).
This causes excessive GC, memory leaks in production and server outage when using EJB (2.0) or anything related to org.jboss.ejb.Container





> org.jboss.ejb.SecurityActions.getMBeanProxy duplicating proxies
> ---------------------------------------------------------------
>
>                 Key: JBAS-3428
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3428
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.0.4.GA
>            Reporter: Clebert Suconic
>         Assigned To: Anil Saldhana
>            Priority: Critical
>             Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.GA
>
>
> Due to JBAS-3013 we changed SecurityActions to use MBeanProxyExt.create what is creating a fake ClassLoader on every call what is forcing Proxy.newInstance to create a new proxy. (Since ClassLoader is a key parameter to a proxy creation).
> This causes excessive GC, memory leaks in production and server outage when using EJB (2.0) or anything related to org.jboss.ejb.Container

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira