Petals ESB Container

"Too many open files" after several component or SA installations/uninstallations

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.1
  • Fix Version/s: 5.0.0
  • Component/s: Installation/Deployment
  • Security Level: Public
  • Description:
    Hide

    After uninstallation or undeployment, the file descriptors associated to the classpath of the uninstalled artifacts are not closed, and the JARs of a dedicated classloader not closed too.
    So after several installation/deployment and uninstallation/undeployment, no more file descriptor is available and an error occurs.
    All open resource must be closed (like file) and static instance must be unreferenced.

    Show
    After uninstallation or undeployment, the file descriptors associated to the classpath of the uninstalled artifacts are not closed, and the JARs of a dedicated classloader not closed too. So after several installation/deployment and uninstallation/undeployment, no more file descriptor is available and an error occurs. All open resource must be closed (like file) and static instance must be unreferenced.
  • Environment:
    OS:all

Issue Links

Depends

Activity

Descending order - Click to sort in ascending order
Hide
Permalink
Christophe DENEUX added a comment - Wed, 27 May 2015 - 07:59:25 +0200

Fixed by PETALSDISTRIB-109

Show
Christophe DENEUX added a comment - Wed, 27 May 2015 - 07:59:25 +0200 Fixed by PETALSDISTRIB-109
Hide
Permalink
Victor NOËL added a comment - Tue, 26 May 2015 - 16:23:48 +0200

Isn't that solved by the switch to Java 7 and the use of close on the classloaders? See PETALSDISTRIB-109.

Show
Victor NOËL added a comment - Tue, 26 May 2015 - 16:23:48 +0200 Isn't that solved by the switch to Java 7 and the use of close on the classloaders? See PETALSDISTRIB-109.
Hide
Permalink
Christophe DENEUX added a comment - Thu, 22 Jul 2010 - 16:40:35 +0200

It's not only a problem into the kernel, but bad Java code in component can cause the problem.
So, we must improve uninstallation/undeployment in the kernel, but also improve our component testing process adding tests about repeated installation/unsinstallation and checking memory consumption

Show
Christophe DENEUX added a comment - Thu, 22 Jul 2010 - 16:40:35 +0200 It's not only a problem into the kernel, but bad Java code in component can cause the problem. So, we must improve uninstallation/undeployment in the kernel, but also improve our component testing process adding tests about repeated installation/unsinstallation and checking memory consumption
Hide
Permalink
Christophe DENEUX added a comment - Thu, 22 Jul 2010 - 16:37:52 +0200

Because the uninstallation/undeployement is not complete, the classloader is not unloaded, so resources are not freed.

Show
Christophe DENEUX added a comment - Thu, 22 Jul 2010 - 16:37:52 +0200 Because the uninstallation/undeployement is not complete, the classloader is not unloaded, so resources are not freed.

People

Dates

  • Created:
    Thu, 22 Jul 2010 - 16:30:11 +0200
    Updated:
    Mon, 5 Oct 2015 - 12:01:45 +0200
    Resolved:
    Wed, 27 May 2015 - 07:59:25 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.