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

JDK11 - GC logging format needs to be reviewed

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • None
    • Scripts, Server

    Description

      • Weird naming of gc log files
        • I test this with JDK11
        • I start standalone and stop standalone
        • JDK10 creates JBOSS_HOME/standalone/log/gc.log (with detailed information) and JBOSS_HOME/standalone/log/gc.log.0 (with brief summary of gc logging)
        • I start standalone and stop standalone again
        • JDK10 moves original gc.log to gc.log.1
        • JDK10 keep original gc.log.0
        • JDK10 creates new gc.log (with detailed information) and gc.log.2 (with brief summary of gc logging)
        • Can this be changed by GC settings?
      • GC logs are much more verbose against jdk8 gc logs. Can this be fixed by some JDK10 gc settings?

      This is follow up for WFCORE-3996

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-15562 Wrong JAVA_OPTS propagation, wrong PowerShell GC logging

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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-15649 (7.4.z) Check and consider to put escaped quotes (\") back to the -Xloggc in standalone.sh

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

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-3996 GC logging is not working on Java 9

          • 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. WFCORE-4147 (WF15) Wrong JAVA_OPTS propagation, wrong PowerShell GC logging

          • 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. WFCORE-4148 Check and consider to put escaped quotes (\") back to the -Xloggc in standalone.sh

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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-14476 GC logging is not working on Java 9+

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

          Activity

            People

              jperkins-rhn James Perkins
              mkopecky@redhat.com Marek Kopecky
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: