[#PETALSDISTRIB-2] Memory-leak on installation/uninstallation and deployment/undeployment - Petals Link JIRA

Details

Type: Bug
Status: New
Priority: Critical
Resolution: Unresolved
Affects Version/s: 4.0.0
Fix Version/s: 5.0.0-M1, 5.2.0, CP-5.2.0, CP-5.4.0
Component/s: None
Security Level: Public

Description:

When installing/uninstalling components and deploying/undeploying services, a memory leak occurs. And after some iteration, the Petals ESB container crashes because of an exception OutOfMemory of the PermGen space of the JVM

Environment:

-

Issue Links

Depends

This issue depends on:
PETALSSEPOJO-15 Memory-leak because service-unit is not unreferenced when shutdowning it if an error occurs during its stop
~~PETALSCDK-83~~ Memory leak because the JBIAcceptorManager.acceptorPool is not freed
~~PETALSDISTRIB-334~~ Upgrade Apache Commons Pool to the version 2.6.0
~~PETALSCDK-76~~ Memory-leak because runtime configuration listeners are not unregistered
~~PETALSCDK-77~~ Memory-leak because utility singletons are not freed
~~PETALSESBCONT-178~~ The RuntimeConfigurationNotifier mbean is not freed when stopping/shutdowning/uninstalling a component, if JVisualVM is connected to the container
~~PETALSBCSOAP-110~~ Memory-leak when uninstalling the BC SOAP because the SOAP engine is not correctly stopped
~~PETALSCDK-80~~ Memory leak because resources of JBIBuilderDescriptor resources are not freed
~~PETALSCDK-82~~ Memory leak because of not static inner classes into the JBIProcessorManager
~~PETALSCDK-85~~ Memory leak because the ThreadGroup of JBIAcceptor is not freed
~~PETALSBCSOAP-113~~ Memory-leak because pools of service clients are not freed
~~PETALSBCSOAP-114~~ Memory-leak because static resources of class Marshaller are not freed
~~PETALSBCSOAP-115~~ Memory leak because of the Jetty logger
~~PETALSCDK-96~~ Memory leak because of a not static inner classe into the AsyncMessageManager

Activity

Descending order - Click to sort in ascending order

Hide

Permalink

Christophe DENEUX added a comment - Mon, 26 Feb 2018 - 09:45:04 +0100 - edited

New memory leak detected caused by Apache Commons Pool that must be upgraded to 2.6.0. Upgrade include in Petals ESB EE 5.2.0

Show

Christophe DENEUX added a comment - Mon, 26 Feb 2018 - 09:45:04 +0100 - edited New memory leak detected caused by Apache Commons Pool that must be upgraded to 2.6.0. Upgrade include in Petals ESB EE 5.2.0

Hide

Permalink

Christophe DENEUX added a comment - Thu, 22 Sep 2016 - 09:22:46 +0200 - edited

Tests postponed to 5.2.1

Show

Christophe DENEUX added a comment - Thu, 22 Sep 2016 - 09:22:46 +0200 - edited Tests postponed to 5.2.1

Hide

Permalink

Christophe DENEUX added a comment - Thu, 1 Oct 2015 - 17:34:32 +0200 - edited

Moving to Java7 should solve several memory leaks. New tests should be done on this purpose to check if memory leaks exist always.

Show

Christophe DENEUX added a comment - Thu, 1 Oct 2015 - 17:34:32 +0200 - edited Moving to Java7 should solve several memory leaks. New tests should be done on this purpose to check if memory leaks exist always.

Hide

Permalink

Christophe DENEUX added a comment - Tue, 26 Jun 2012 - 11:12:00 +0200 - edited

Partially resolved in version 4.1.0.
New fixes will be added in the next version of the distribution

Show

Christophe DENEUX added a comment - Tue, 26 Jun 2012 - 11:12:00 +0200 - edited Partially resolved in version 4.1.0. New fixes will be added in the next version of the distribution

Hide

Permalink

Christophe DENEUX added a comment - Thu, 8 Mar 2012 - 10:06:52 +0100 - edited

Some memory leaks are located into the Petals kernel:

~~PETALSESBCONT-178~~

Some others are located into components at CDK level, and the components will need to upgrade the version of the CDK they use:

Some others are located directly in components:

Show

Christophe DENEUX added a comment - Thu, 8 Mar 2012 - 10:06:52 +0100 - edited Some memory leaks are located into the Petals kernel:

~~PETALSESBCONT-178~~

Some others are located into components at CDK level, and the components will need to upgrade the version of the CDK they use:

Some others are located directly in components:

Petals Distribution

Memory-leak on installation/uninstallation and deployment/undeployment

Details

Issue Links

Activity

People

Dates