glassfish
  1. glassfish
  2. GLASSFISH-13593

Logging is terminated too early during appserver shutdown

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 3.1
    • Fix Version/s: 3.1_dev
    • Component/s: logging
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: Linux

    • Issuezilla Id:
      13,593

      Description

      When the appserver is being shutdown, the logging process is being terminated
      too early and messages being logged from various subsystems within the appserver
      during shutdown are being lost. Below is an example of the last messages written
      to the log. The data about what happened during shutdown has been lost. Turning
      logging off must be done at the last possible moment.

      [#|2010-09-23T11:30:59.555-0700|INFO|glassfish3.1|javax.enterprise.system.tools.admin.com.sun.enterprise.v3.admin.cluster|_ThreadID=15;_ThreadName=Thread-1;|Server
      shutdown initiated|#]

      [#|2010-09-23T11:30:59.564-0700|INFO|glassfish3.1|org.glassfish.osgijavaeebase|_ThreadID=15;_ThreadName=Thread-1;|Stopping
      extender called org.glassfish.osgiweb.WebExtender@309a5663|#]

      Referring to issue tracker GLASSFISH-13592 for a description of my test scenario

      During the test I was conducting, asadmin stop-local-instance was executed but
      failed (timed out after 60 seconds). As a result, the appserver was left in an
      inconsistent state where the http service was stop yet my ejb webapp and the GMS
      service were still active and actively logging messages that were not being
      written into the log file. We know these service were active because we received
      messages from them in the das and other instances. The logging information
      during the failed shutdown is critical to diagnose GLASSFISH-13592

        Issue Links

          Activity

          Hide
          Joe Fialli added a comment -

          I wanted to add some additional information on how GMS is getting shutdown.
          I was able to get this information from running in glassfish interactive mode
          since logging continues to work during stop in this mode.

          Here is how I started the DAS in this mode.

          %java -DGlassFish_Interactive=true -jar
          glassfishv3/glassfish/modules/glassfish.jar -domain mydomain

          The following log messages show the stack trace on how GMS has registered to be
          notified on server shutdown and when gms calls the method "shutdown" that
          terminates its processing.

          [#|2010-10-05T08:44:10.452-0400|INFO|glassfish3.1|null|_ThreadID=1;_ThreadName=main;|command
          = stop|#]

          [#|2010-10-05T08:44:10.457-0400|INFO|glassfish3.1|org.glassfish.osgijavaeebase|_ThreadID=1;_ThreadName=main;|Stopping
          extender called org.glassfish.osgiweb.WebExtender@432398ed|#]

          [#|2010-10-05T08:44:10.466-0400|INFO|glassfish3.1|org.glassfish.osgijavaeebase|_ThreadID=1;_ThreadName=main;|Stopping
          extender called org.glassfish.osgijavaeebase.JavaEEExtender@3ff0efca|#]

          [#|2010-10-05T08:44:10.652-0400|INFO|glassfish3.1|null|_ThreadID=81;_ThreadName=fileinstall-/gf/glassfishv3/glassfish/modules/autostart/;|Installed
          /gf/glassfishv3/glassfish/modules/autostart/org.apache.felix.webconsole.internal.servlet.OsgiManager.cfg|#]

          [#|2010-10-05T08:44:10.657-0400|INFO|glassfish3.1|null|_ThreadID=81;_ThreadName=fileinstall-/gf/glassfishv3/glassfish/modules/autostart/;|Installed
          /gf/glassfishv3/glassfish/modules/autostart/org.apache.felix.fileinstall-autodeploy-bundles.cfg|#]

          [#|2010-10-05T08:44:10.659-0400|INFO|glassfish3.1|null|_ThreadID=14;_ThreadName=Configuration
          Updater;|/gf/glassfishv3/glassfish/domains/mydomain/autodeploy/bundles does not
          exist, please create it.|#]

          [#|2010-10-05T08:44:10.915-0400|INFO|glassfish3.1|javax.org.glassfish.gms.org.glassfish.gms|_ThreadID=1;_ThreadName=main;|GMSAD1008:
          GMSAdapter for member: server group: myCluster received GlassfishEventType:
          org.glassfish.api.event.EventListener$Event@1df37bf1|#]

          [#|2010-10-05T08:44:10.916-0400|INFO|glassfish3.1|javax.org.glassfish.gms.org.glassfish.gms|_ThreadID=1;_ThreadName=main;|GMSAdapterImpl.GlassfishEventListner(SERVER_SHUTDOWN
          java.lang.Exception: stack trace
          at org.glassfish.gms.GMSAdapterImpl$1.event(GMSAdapterImpl.java:544)
          at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:128)
          at com.sun.enterprise.v3.server.AppServerStartup.stop(AppServerStartup.java:410)
          at com.sun.enterprise.glassfish.bootstrap.GlassFishImpl.stop(GlassFishImpl.java:88)
          at
          com.sun.enterprise.glassfish.bootstrap.GlassFishMain$Launcher.startConsole(GlassFishMain.java:143)
          at
          com.sun.enterprise.glassfish.bootstrap.GlassFishMain$Launcher.launch(GlassFishMain.java:122)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
          at
          sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:597)
          at
          com.sun.enterprise.glassfish.bootstrap.GlassFishMain.main(GlassFishMain.java:104)
          at com.sun.enterprise.glassfish.bootstrap.ASMain.main(ASMain.java:55)

          #]

          [#|2010-10-05T08:44:10.917-0400|INFO|glassfish3.1|ShoalLogger|_ThreadID=1;_ThreadName=main;|GMS1096:
          Member server is leaving group myCluster|#]

          [#|2010-10-05T08:44:10.917-0400|INFO|glassfish3.1|ShoalLogger|_ThreadID=1;_ThreadName=main;|GMS1010:
          Leaving GMS group myCluster with shutdown type set to InstanceShutdown|#]

          [#|2010-10-05T08:44:10.922-0400|INFO|glassfish3.1|ShoalLogger|_ThreadID=23;_ThreadName=IP
          Multicast Listener for /228.9.1.3:2231;|GMS1110: Thread IP Multicast Listener
          for /228.9.1.3:2231 has completed.|#]

          [#|2010-10-05T08:44:10.923-0400|CONFIG|glassfish3.1|ShoalLogger|_ThreadID=25;_ThreadName=MasterNode
          processOutStandingMessages;|GMS1065: Completed processing outstanding master
          node messages for member:server group:myCluster outstandingMessages to process:0|#]

          [#|2010-10-05T08:44:10.924-0400|INFO|glassfish3.1|ShoalLogger.monitor|_ThreadID=1;_ThreadName=main;|BlockingIOMulicastSender
          monitoring stats: received: 22 core poolsize:10 largest pool size:10 task
          count:22 max queue size:0 rejected execution:0|#]

          [#|2010-10-05T08:44:10.938-0400|INFO|glassfish3.1|ShoalLogger.monitor|_ThreadID=1;_ThreadName=main;|GMS1115:
          router signal queue high water mark:0 signal queue capacity:600|#]

          [#|2010-10-05T08:44:10.939-0400|INFO|glassfish3.1|org.glassfish.ha.store.adapter.cache.ShoalBackingStoreProxy|_ThreadID=1;_ThreadName=main;|Unregistered
          SHOAL BackingStore Proxy with persistence-type = replicated|#]

          [#|2010-10-05T08:44:10.939-0400|INFO|glassfish3.1|org.glassfish.ha.store.adapter.cache.ReplicationStoreProxy2|_ThreadID=1;_ThreadName=main;|Unregistered
          ReplicationStoreProxy with persistence-type = replication|#]

          [#|2010-10-05T08:44:10.939-0400|INFO|glassfish3.1|ShoalLogger|_ThreadID=19;_ThreadName=ViewWindowThread:myCluster;|GMS1091:
          View Window event processing thread for group myCluster terminated normally|#]

          [#|2010-10-05T08:44:10.939-0400|INFO|glassfish3.1|ShoalLogger|_ThreadID=20;_ThreadName=MessageWindowThread:myCluster;|GMS1088:
          MessageWindow thread for group myCluster terminated due to shutdown notification|#]

          [#|2010-10-05T08:44:10.940-0400|INFO|glassfish3.1|ShoalLogger|_ThreadID=18;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router
          Thread;|GMS1107: SignalHandler task named
          com.sun.enterprise.ee.cms.impl.common.Router Thread exiting|#]

          [#|2010-10-05T08:44:10.953-0400|INFO|glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=1;_ThreadName=main;|JMXStartupService:
          Stopped JMXConnectorServer:
          service:jmx:rmi://dhcp-burlington9-3rd-a-east-10-152-23-224.usdhcp.oraclecorp.com:8686/jndi/rmi://dhcp-burlington9-3rd-a-east-10-152-23-224.usdhcp.oraclecorp.com:8686/jmxrmi|#]

          [#|2010-10-05T08:44:10.955-0400|INFO|glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=1;_ThreadName=main;|JMXStartupService
          and JMXConnectors have been shut down.|#]

          [#|2010-10-05T08:44:10.960-0400|INFO|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=1;_ThreadName=main;|Shutdown
          procedure finished|#]

          [#|2010-10-05T08:44:10.961-0400|INFO|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=86;_ThreadName=GlassFish
          Kernel Main Thread;|[Thread[GlassFish Kernel Main Thread,5,main]] exiting|#]

          Show
          Joe Fialli added a comment - I wanted to add some additional information on how GMS is getting shutdown. I was able to get this information from running in glassfish interactive mode since logging continues to work during stop in this mode. Here is how I started the DAS in this mode. %java -DGlassFish_Interactive=true -jar glassfishv3/glassfish/modules/glassfish.jar -domain mydomain The following log messages show the stack trace on how GMS has registered to be notified on server shutdown and when gms calls the method "shutdown" that terminates its processing. [#|2010-10-05T08:44:10.452-0400|INFO|glassfish3.1|null|_ThreadID=1;_ThreadName=main;|command = stop|#] [#|2010-10-05T08:44:10.457-0400|INFO|glassfish3.1|org.glassfish.osgijavaeebase|_ThreadID=1;_ThreadName=main;|Stopping extender called org.glassfish.osgiweb.WebExtender@432398ed|#] [#|2010-10-05T08:44:10.466-0400|INFO|glassfish3.1|org.glassfish.osgijavaeebase|_ThreadID=1;_ThreadName=main;|Stopping extender called org.glassfish.osgijavaeebase.JavaEEExtender@3ff0efca|#] [#|2010-10-05T08:44:10.652-0400|INFO|glassfish3.1|null|_ThreadID=81;_ThreadName=fileinstall-/gf/glassfishv3/glassfish/modules/autostart/;|Installed /gf/glassfishv3/glassfish/modules/autostart/org.apache.felix.webconsole.internal.servlet.OsgiManager.cfg|#] [#|2010-10-05T08:44:10.657-0400|INFO|glassfish3.1|null|_ThreadID=81;_ThreadName=fileinstall-/gf/glassfishv3/glassfish/modules/autostart/;|Installed /gf/glassfishv3/glassfish/modules/autostart/org.apache.felix.fileinstall-autodeploy-bundles.cfg|#] [#|2010-10-05T08:44:10.659-0400|INFO|glassfish3.1|null|_ThreadID=14;_ThreadName=Configuration Updater;|/gf/glassfishv3/glassfish/domains/mydomain/autodeploy/bundles does not exist, please create it.|#] [#|2010-10-05T08:44:10.915-0400|INFO|glassfish3.1|javax.org.glassfish.gms.org.glassfish.gms|_ThreadID=1;_ThreadName=main;|GMSAD1008: GMSAdapter for member: server group: myCluster received GlassfishEventType: org.glassfish.api.event.EventListener$Event@1df37bf1|#] [#|2010-10-05T08:44:10.916-0400|INFO|glassfish3.1|javax.org.glassfish.gms.org.glassfish.gms|_ThreadID=1;_ThreadName=main;|GMSAdapterImpl.GlassfishEventListner(SERVER_SHUTDOWN java.lang.Exception: stack trace at org.glassfish.gms.GMSAdapterImpl$1.event(GMSAdapterImpl.java:544) at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:128) at com.sun.enterprise.v3.server.AppServerStartup.stop(AppServerStartup.java:410) at com.sun.enterprise.glassfish.bootstrap.GlassFishImpl.stop(GlassFishImpl.java:88) at com.sun.enterprise.glassfish.bootstrap.GlassFishMain$Launcher.startConsole(GlassFishMain.java:143) at com.sun.enterprise.glassfish.bootstrap.GlassFishMain$Launcher.launch(GlassFishMain.java:122) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.enterprise.glassfish.bootstrap.GlassFishMain.main(GlassFishMain.java:104) at com.sun.enterprise.glassfish.bootstrap.ASMain.main(ASMain.java:55) #] [#|2010-10-05T08:44:10.917-0400|INFO|glassfish3.1|ShoalLogger|_ThreadID=1;_ThreadName=main;|GMS1096: Member server is leaving group myCluster|#] [#|2010-10-05T08:44:10.917-0400|INFO|glassfish3.1|ShoalLogger|_ThreadID=1;_ThreadName=main;|GMS1010: Leaving GMS group myCluster with shutdown type set to InstanceShutdown|#] [#|2010-10-05T08:44:10.922-0400|INFO|glassfish3.1|ShoalLogger|_ThreadID=23;_ThreadName=IP Multicast Listener for /228.9.1.3:2231;|GMS1110: Thread IP Multicast Listener for /228.9.1.3:2231 has completed.|#] [#|2010-10-05T08:44:10.923-0400|CONFIG|glassfish3.1|ShoalLogger|_ThreadID=25;_ThreadName=MasterNode processOutStandingMessages;|GMS1065: Completed processing outstanding master node messages for member:server group:myCluster outstandingMessages to process:0|#] [#|2010-10-05T08:44:10.924-0400|INFO|glassfish3.1|ShoalLogger.monitor|_ThreadID=1;_ThreadName=main;|BlockingIOMulicastSender monitoring stats: received: 22 core poolsize:10 largest pool size:10 task count:22 max queue size:0 rejected execution:0|#] [#|2010-10-05T08:44:10.938-0400|INFO|glassfish3.1|ShoalLogger.monitor|_ThreadID=1;_ThreadName=main;|GMS1115: router signal queue high water mark:0 signal queue capacity:600|#] [#|2010-10-05T08:44:10.939-0400|INFO|glassfish3.1|org.glassfish.ha.store.adapter.cache.ShoalBackingStoreProxy|_ThreadID=1;_ThreadName=main;|Unregistered SHOAL BackingStore Proxy with persistence-type = replicated|#] [#|2010-10-05T08:44:10.939-0400|INFO|glassfish3.1|org.glassfish.ha.store.adapter.cache.ReplicationStoreProxy2|_ThreadID=1;_ThreadName=main;|Unregistered ReplicationStoreProxy with persistence-type = replication|#] [#|2010-10-05T08:44:10.939-0400|INFO|glassfish3.1|ShoalLogger|_ThreadID=19;_ThreadName=ViewWindowThread:myCluster;|GMS1091: View Window event processing thread for group myCluster terminated normally|#] [#|2010-10-05T08:44:10.939-0400|INFO|glassfish3.1|ShoalLogger|_ThreadID=20;_ThreadName=MessageWindowThread:myCluster;|GMS1088: MessageWindow thread for group myCluster terminated due to shutdown notification|#] [#|2010-10-05T08:44:10.940-0400|INFO|glassfish3.1|ShoalLogger|_ThreadID=18;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router Thread;|GMS1107: SignalHandler task named com.sun.enterprise.ee.cms.impl.common.Router Thread exiting|#] [#|2010-10-05T08:44:10.953-0400|INFO|glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=1;_ThreadName=main;|JMXStartupService: Stopped JMXConnectorServer: service:jmx:rmi://dhcp-burlington9-3rd-a-east-10-152-23-224.usdhcp.oraclecorp.com:8686/jndi/rmi://dhcp-burlington9-3rd-a-east-10-152-23-224.usdhcp.oraclecorp.com:8686/jmxrmi|#] [#|2010-10-05T08:44:10.955-0400|INFO|glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=1;_ThreadName=main;|JMXStartupService and JMXConnectors have been shut down.|#] [#|2010-10-05T08:44:10.960-0400|INFO|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=1;_ThreadName=main;|Shutdown procedure finished|#] [#|2010-10-05T08:44:10.961-0400|INFO|glassfish3.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=86;_ThreadName=GlassFish Kernel Main Thread;|[Thread [GlassFish Kernel Main Thread,5,main] ] exiting|#]
          Hide
          marina vatkina added a comment -

          Messages about EJB Timer Service shutdown are also lost most of the time.

          Show
          marina vatkina added a comment - Messages about EJB Timer Service shutdown are also lost most of the time.
          Hide
          naman_mehta added a comment -

          It's not specific issue to Logging Cod or Logging service. Had discussion is
          going on with Tom, Byron, Shreedhar on the same.

          My investigation for the same as below:
          When I run the stop-command. It goes through StopServer.java in which code is
          executing "System.exit(0);". Due to this it calls shutdown hooks for glassfish
          and logging.

          JStack for the same:

          Thread-66@9262 daemon, prio=5, in group 'grizzly-kernel', status: 'WAIT'
          at java.lang.Object.wait(Object.java:-1)
          at java.lang.Thread.join(Thread.java:1143)
          at java.lang.Thread.join(Thread.java:1196)
          at java.lang.ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:79)
          at java.lang.ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:24)
          at java.lang.Shutdown.runHooks(Shutdown.java:79)
          at java.lang.Shutdown.sequence(Shutdown.java:123)
          at java.lang.Shutdown.exit(Shutdown.java:168)
          at java.lang.Runtime.exit(Runtime.java:90)
          at java.lang.System.exit(System.java:904)
          at com.sun.enterprise.v3.admin.StopServer.doExecute(StopServer.java:74)
          at
          com.sun.enterprise.v3.admin.StopDomainCommand.execute(StopDomainCommand.java:103)
          at
          com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:360)
          at
          com.sun.enterprise.v3.admin.CommandRunnerImpl$2.run(CommandRunnerImpl.java:388)

          Thread-0@9265, prio=5, in group 'main', status: 'RUNNING'
          at java.util.logging.Logger.removeHandler(Logger.java:1181)
          at java.util.logging.LogManager$RootLogger.removeHandler(LogManager.java:975)
          at java.util.logging.LogManager.resetLogger(LogManager.java:680)
          at java.util.logging.LogManager.reset(LogManager.java:665)
          at java.util.logging.LogManager$Cleaner.run(LogManager.java:223)

          Here, all shutdown hooks runs concurrently so before it executes glassfish hooks
          it makes call to logging hooks which in turn clears all handlers assign to
          RootLogger and it fails to log data in server.log file.

          More details for shutdown hooks:
          http://download-llnw.oracle.com/javase/6/docs/api/java/lang/Runtime.html#addShutdownHook%28java.lang.Thread%29

          To avoid this we need to stop calling system.exit before any GF services stop.

          Show
          naman_mehta added a comment - It's not specific issue to Logging Cod or Logging service. Had discussion is going on with Tom, Byron, Shreedhar on the same. My investigation for the same as below: When I run the stop-command. It goes through StopServer.java in which code is executing "System.exit(0);". Due to this it calls shutdown hooks for glassfish and logging. JStack for the same: Thread-66@9262 daemon, prio=5, in group 'grizzly-kernel', status: 'WAIT' at java.lang.Object.wait(Object.java:-1) at java.lang.Thread.join(Thread.java:1143) at java.lang.Thread.join(Thread.java:1196) at java.lang.ApplicationShutdownHooks.runHooks(ApplicationShutdownHooks.java:79) at java.lang.ApplicationShutdownHooks$1.run(ApplicationShutdownHooks.java:24) at java.lang.Shutdown.runHooks(Shutdown.java:79) at java.lang.Shutdown.sequence(Shutdown.java:123) at java.lang.Shutdown.exit(Shutdown.java:168) at java.lang.Runtime.exit(Runtime.java:90) at java.lang.System.exit(System.java:904) at com.sun.enterprise.v3.admin.StopServer.doExecute(StopServer.java:74) at com.sun.enterprise.v3.admin.StopDomainCommand.execute(StopDomainCommand.java:103) at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:360) at com.sun.enterprise.v3.admin.CommandRunnerImpl$2.run(CommandRunnerImpl.java:388) Thread-0@9265, prio=5, in group 'main', status: 'RUNNING' at java.util.logging.Logger.removeHandler(Logger.java:1181) at java.util.logging.LogManager$RootLogger.removeHandler(LogManager.java:975) at java.util.logging.LogManager.resetLogger(LogManager.java:680) at java.util.logging.LogManager.reset(LogManager.java:665) at java.util.logging.LogManager$Cleaner.run(LogManager.java:223) Here, all shutdown hooks runs concurrently so before it executes glassfish hooks it makes call to logging hooks which in turn clears all handlers assign to RootLogger and it fails to log data in server.log file. More details for shutdown hooks: http://download-llnw.oracle.com/javase/6/docs/api/java/lang/Runtime.html#addShutdownHook%28java.lang.Thread%29 To avoid this we need to stop calling system.exit before any GF services stop.
          Hide
          naman_mehta added a comment -

          This issue depends on 13780 so waiting for the fix. Changing milestone to ms07.

          Show
          naman_mehta added a comment - This issue depends on 13780 so waiting for the fix. Changing milestone to ms07.
          Hide
          Tom Mueller added a comment -

          The root cause of this problem is that the shutdown method isn't actually shutting
          down the server. This is due to a bug in the StopServer.doExecute() method which
          uses the wrong module name to identify the GlassFish object.

          Show
          Tom Mueller added a comment - The root cause of this problem is that the shutdown method isn't actually shutting down the server. This is due to a bug in the StopServer.doExecute() method which uses the wrong module name to identify the GlassFish object.
          Hide
          Sanjeeb Sahoo added a comment -

          I have filed issue 14523 to fix the shutdown sequence so that this issue can
          just deal with the logging part.

          Show
          Sanjeeb Sahoo added a comment - I have filed issue 14523 to fix the shutdown sequence so that this issue can just deal with the logging part.
          Hide
          naman_mehta added a comment -

          Created an attachment (id=5488)
          Server.log file for same.

          Show
          naman_mehta added a comment - Created an attachment (id=5488) Server.log file for same.
          Hide
          naman_mehta added a comment -

          I verified the changes after the depending issues fixed. It's logging all
          messages under server.log file similar to the interactive mode.

          so now interactive mode start/stop and asadmin start/stop command logs similar
          messages. I have attached the log file for the same.

          Show
          naman_mehta added a comment - I verified the changes after the depending issues fixed. It's logging all messages under server.log file similar to the interactive mode. so now interactive mode start/stop and asadmin start/stop command logs similar messages. I have attached the log file for the same.

            People

            • Assignee:
              naman_mehta
              Reporter:
              Stephen DiMilla
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: