Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-340

Memory leak in JBoss CLI

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.0.DR9
    • 7.0.0.DR2
    • CLI
    • None
    • Hide

      Simply create new `CommandContextImpl` instances:

      while (true) {
  CommandContextFactory.getInstance().newCommandContext();
}
      Show
      Simply create new `CommandContextImpl` instances: while ( true ) { CommandContextFactory.getInstance().newCommandContext(); }

    Description

      The JBoss CLI contains a memory leak related to CLI Kerberos authentication.

      The org.jboss.as.cli.impl.CommandContextImpl class calls the initJaasConfig() in its constructor,
      which adds a new JaasConfigurationWrapper instance to javax.security.auth.login.Configuration.
      It's done for every new CommandContext instance, so it consumes more and more memory. There is no cleanup for the registered
      configurations.

      Moreover, the searches for appropriate
      login config take more and more time because they have to go through all the wrapped objects.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-774 Memory leak in JBoss CLI

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              olubyans@redhat.com Alexey Loubyansky
              josef.cacek@gmail.com Josef Cacek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: