Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-273

Upgrade to JRuby 1.7.19 / fix for jruby-pool DELETE memory leak

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: SERVER 1.0.0
    • Fix Version/s: SERVER 1.0.8, SERVER 2.1.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Epic Link:
    • Sub-team:
    • Story Points:
      1
    • Sprint:
      Server Emerald 2015-03-04, Server 2015-02-18, Server Jade 2015-03-18

      Description

      In doing some memory leak analysis for SERVER-219, I found a memory leak in JRuby. Even after terminate is called on a ScriptingContainer, three ChannelDescriptor objects – related to STDIN, STDERR, and STDOUT – and a few related objects are leaked. This leak would be manifested in Puppet Server around invocations of the "jruby-pool" DELETE admin API.

      An issue was filed to the JRuby project as https://github.com/jruby/jruby/issues/2333. A fix has already been implemented for the problem and is scheduled to be delivered in JRuby 1.7.19.

      This ticket is just a reminder to track the JRuby issue and test a fix when available in an upgrade to Puppet Server's JRuby dependency.

        Attachments

          Issue Links

          relates to

          Task - A task that needs to be done. SERVER-219 Test ScriptingContainer terminate for possible memory leaks

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed
          links to

          Web Link PR

            Activity

              People

              Assignee:
              erik Erik Dasher
              Reporter:
              jeremy.barlow Jeremy Barlow
              QA Contact:
              Erik Dasher Erik Dasher
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support