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

[GSS](7.0.z) Monthly file rotation will continually overwrite the rotated log file

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.8.CR1, 7.0.8.GA
    • 7.0.6.GA, 7.1.0.ER1
    • Logging
    • None
    • EAP 7.0.8

    Description

      When the next rollover time is calculated a java.util.Calendar is used. When rotated monthly the day of the week is set to 0 and 1 month is added. This causes the calendar to be set to the last day of the current month.

      On the last day of the month this also causes the file to continually rotate with each log message written, overwriting the previous log message.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-11997 [GSS](7.1.0) Monthly file rotation will continually overwrite the rotated log file

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

          Bug - A problem that impairs or prevents the functions of the product. LOGMGR-163 Monthly file rotation will continually overwrite the rotated log file

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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-10689 (7.0.z) Upgrade jboss-logmanager from 2.0.3.Final to 2.0.7.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.
          • Verified
          links to

          Web Link KCS

          Activity

            People

              jperkins-rhn James Perkins
              rhn-support-bmaxwell Brad Maxwell
              Jiří Bílek Jiří Bílek (Inactive)
              Jiří Bílek Jiří Bílek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: