Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: JBossAS-4.0.3RC1
    • Fix Version/s: JBossAS-4.0.3 Final
    • Component/s: Other
    • Labels:
      None
    • Environment:

      All Sun JVMs

      Description

      Sun's LogManager has an undocumented feature where System.exit()
      invokes reset() on the LogManager.

      This causes problems for other Shutdown hooks like JBoss's that stops all services.
      i.e. the loggers can be reset while another shutdown hook still wants to use them

      A potential fix is to set the system property to install our own LogManager that
      disables reset. Instead we do the reset processing from
      our own shutdown hook.

      // psuedo code
      public class JBossLogManager extends LogManager
      {
      protected JBossLogManager()
      {
      }

      public void reset()

      { // do nothing }

      public void jbossReset()

      { super.reset(); }

      }

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                starksm64 Scott Stark
                Reporter:
                adrian.brock Adrian Brock
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: