[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2763) jBPM 4.3 - InitialContext is not closed after being used for JNDI Lookup (Multiple classes)

[Santanu Saraswati (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBPM-2763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12507905#action_12507905 ] 

Santanu Saraswati commented on JBPM-2763:
-----------------------------------------

Wont they be garbage collected anyway? Do we really need to do anything there? It needs to be confirmed that there is really a problem (which I believe is not there :-)). 

> jBPM 4.3 - InitialContext is not closed after being used for JNDI Lookup (Multiple classes)
> -------------------------------------------------------------------------------------------
>
>                 Key: JBPM-2763
>                 URL: https://jira.jboss.org/jira/browse/JBPM-2763
>             Project: jBPM
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Runtime Engine
>    Affects Versions: jBPM 4.3
>            Reporter: Martin Porter
>
> In various classes when an InitialContext is created it is not closed before the method returns. The following classes have this issue:-
> org.jboss.bpm.console.server.util.InvocationProxy
> org.jbpm.jpdl.internal.activity.JavaActivity
> org.jbpm.jpdl.internal.activity.JmsActivity
> org.jbpm.pvm.internal.cfg.ConfigurationImpl
> org.jbpm.pvm.internal.processengine.ProcessEngineImpl
> org.jbpm.pvm.internal.tx.JtaTransaction
> org.jbpm.pvm.internal.wire.descriptor.JbossIdmIdentitySessionFactoryDescriptor
> org.jbpm.pvm.internal.wire.descriptor.JndiDescriptor
> Hence this will result in memory leaks and also issues with hot deployment for EAR's containing the process engine.

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