Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-3076

Infinispan should enable use of log4j2

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 8.0.0.Beta2, 8.0.0.Final
    • 5.2.5.Final, 6.0.0.Final
    • Core
    • None

    Description

      log4j locks up on a certain amount of load, especially under concurrent access. The recommendation was to move up to log4j2. This can be done by removing
      1 JAR (log4j.jar) and adding 2 JARs (log4j-bridge and log4j-core.jar).

      Also refer: https://issues.jboss.org/browse/ISPN-2976

      Attachments

        Issue Links

          is blocked by

          Feature Request - Feature requests from customers and/or users JBLOGGING-107 JBoss Logging throws NullPointerException when used with Log4j 2.0 final.

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JBLOGGING-94 JBoss Logging does not detect log4j 2.0

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBLOGGING-95 Add Logger/LoggerProvider to support new Log4j 2 to improve performance

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved
          is related to

          Task - Represents a small unit of work that is not end-user facing. JGRP-1585 Add support for log4j2

          • 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

          Task - Represents a small unit of work that is not end-user facing. ISPN-2976 Log4J dependencies in codebase to be cleaned up

          • 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.
          • Closed

          Activity

            People

              ttarrant@redhat.com Tristan Tarrant
              dmehra_jira Divya Mehra (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: