7 Replies Latest reply on Jan 25, 2010 1:21 PM by Ronald van Kuijk

    jBPM 4.3 - Will cause memory leaks due to unclosed InitialContext()

    M Porter Newbie

      Hi,

       

      Further to my previous post regarding JTA transactions and upon my concern at finding an unclosed InitialContext I did a search through the jBPM source code and to my amazement I found that this is in fact commonplace. And this same issue can be found throughout the a number of classes in the code base.

       

      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

       

      This means that the current distribution of 4.3 could simply not be used in a real production scenario due to memory leaks and issues with redployments.


      Regards

      Martin