Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-5781

Remove log4j 1.x module and support

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 19.0.0.Beta13, 19.0.0.Final
    • None
    • None
    • None

    Description

      Overview

      WildFly currently includes a module org.apache.log4j which is an alias for org.jboss.log4j.logmnager. log4j 1.x reached end of life in August of 2015. It is time for it's removal from WildFly as there will be no more fixes applied to log4j.

      Impact

      There is some impact to this decision. The following options will no longer be supported:

      • If you use log4j in your deployment and do not include a log4j configuration file, then you must either migrate to a new logging facade or add a log4j configuration to your deployment. Log messages will no longer be routed based on the logging subsystem.
      • If you use a log4j.xml, log4j.properties or jboss-log4j.xml file in your deployment you must include a log4j.jar in your deployment. Note if it's a jboss-log4j.xml you'll need to rename the file.
      • custom-handler's will no longer allow log4j appenders to be used

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. WFLY-15666 log4j-jboss-logmanager -- Move WildFly Preview to a native jakarta namespace variant

          • 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
          is blocked by

          Task - Represents a small unit of work that is not end-user facing. WFCORE-5784 Deprecate the org.apache.log4j module

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

          Bug - A problem that impairs or prevents the functions of the product. WFLY-16282 Update log4j-jboss-logmanager-1.3.0.Final.jar in wildfly as it has dependency on log4j1 jars.

          • 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

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-1656 log4j per logging deployment configuration errors are swallowed

          • 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

          Task - Represents a small unit of work that is not end-user facing. WFLY-16538 Remove usages of log4j where applicable and update documentation for removal of log4j 1.x

          • 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

              jperkins-rhn James Perkins
              jperkins-rhn James Perkins
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: