Petals ESB Container

OOM in PermGen space when attaching or detaching a container to/from a topology

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 5.0.0
Fix Version/s: 5.0.1
Component/s: Topology/network
Security Level: Public

Description:
Hide
When looping about attachment and detachment of a container, a out of memory can occurs because no more memory is available into the PermGen space.
It is due to a memory leak on container attachment and container detachment, following objects are not freed:

shared library classloaders,

component classloaders,

component bootstrap thread,

component installer.
Show
When looping about attachment and detachment of a container, a out of memory can occurs because no more memory is available into the PermGen space. It is due to a memory leak on container attachment and container detachment, following objects are not freed:

shared library classloaders,

component classloaders,

component bootstrap thread,

component installer.

Environment:

-

Download all attachments as a ZIP file

Attachments

build-concurrent-attachments-detachments.xml

(84 kB)

Christophe DENEUX

Wed, 18 Nov 2015 - 12:16:06 +0100

Issue Links

Depends

This issue depends on:
~~PETALSESBCONT-359~~ JBI artifact lifecycle not linked to their associated Fractal components
~~PETALSESBCONT-364~~ "No endpoint(s) matching the target service" when attaching a container

Activity

People

Assignee:

Christophe DENEUX

Reporter:

Christophe DENEUX
Watchers:

0

Dates

Created:

Tue, 17 Nov 2015 - 16:36:05 +0100

Updated:

Thu, 26 Nov 2015 - 16:51:02 +0100

Resolved:

Thu, 26 Nov 2015 - 16:51:02 +0100