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

Upgrade jboss-logmanager from 2.1.4.Final to 2.1.5.Final

    XMLWordPrintable

Details

    • Component Upgrade
    • Resolution: Done
    • Major
    • 7.2.0.GA
    • None
    • Logging
    • None

    Description

      Upgrade org.jboss.logmanager:jboss-logmanager from 2.1.4.Final to 2.1.5.Final.

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. WFLY-11109 Fix PatterFormatter documentation for host name pattern

          • 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
          clones

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-4151 Upgrade jboss-logmanager from 2.1.4.Final to 2.1.5.Final

          • 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
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. LOGMGR-200 SSLProtocolException: Connection reset on JDK11

          • 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. LOGMGR-201 SysLogHandler doesn't log null or empty message

          • 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. LOGMGR-203 LogManager stops any logging output after changing "encoding" attribute to file-handler

          • 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. LOGMGR-204 Short host name format yields last part of name instead of first part

          • 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. LOGMGR-206 Qualified host name should use right based precision instead of left

          • 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. LOGMGR-202 Some fields are not copied by the copy constructor of ExtLogRecord

          • 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 duplicated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-15529 (7.2.z) Upgrade logmanager from 2.1.4 to 2.1.5.Final

          • 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

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

              Dates

                Created:
                Updated:
                Resolved: