CDV ❯ Woud like Terracotta log to give clear indication of stop completion
-
New Feature
-
Status: Open
-
2 Major
-
Resolution:
-
-
-
prodmgmt
-
Reporter: mkalstei
-
July 27, 2009
-
0
-
Watchers: 0
-
March 19, 2010
-
Description
Product/Component: Terracotta
Version: Terracotta 2.7.3
Description: After ./stop-tc-server.sh stop, the log only has “Server exiting…” It should say “Server successfully exited” afterwards, or Moved to state [ something that shows it is stopped ] example log: [cguser@bzcgconlgmt01 fptool]$ cat terracotta-start_bzcgconlgmt01.log 2009-07-22 16:59:26,390 INFO - Terracotta 2.7.3, as of 20090129-100125 (Revision 11424 by cruise@su10mo5 from 2.7) 2009-07-22 16:59:26,852 INFO - Configuration loaded from the file at ‘/dg/bnzi/apps/fptool/tc-config.xml’. 2009-07-22 16:59:26,875 INFO - Log file: ‘/dg/bnzi/apps/fptool/log/terracotta/bzcgconlgmt01/bzcgconlgmt01/server-logs/terracotta-server.log’. 2009-07-22 16:59:29,356 INFO - Statistics store: ‘/dg/bnzi/apps/fptool/log/terracotta/bzcgconlgmt01/bzcgconlgmt01/server-statistics’. 2009-07-22 16:59:29,364 INFO - Available Max Runtime Memory: 490MB 2009-07-22 16:59:31,798 INFO - Statistics buffer: ‘/dg/bnzi/apps/fptool/log/terracotta/bzcgconlgmt01/bzcgconlgmt01/server-statistics’. 2009-07-22 16:59:31,870 INFO - JMX Server started. Available at URL[service:jmx:jmxmp://0.0.0.0:9520] 2009-07-22 16:59:32,688 INFO - NodeID[bzcgconlgmt02:9530] joined the cluster 2009-07-22 16:59:32,696 INFO - Moved to State[ PASSIVE-UNINITIALIZED ] 2009-07-22 16:59:32,785 INFO - Moved to State[ PASSIVE-STANDBY ] 2009-07-22 17:09:07,167 INFO - Server exiting…
Expected Behavior: Server exiting… as the only message makes it look like the server is hung trying to shut down.
Actual Behavior: Should be a specific message saying the server is stopped or terminated. Note that the stdout has a good message, this should duplicate into the logs.
Workaround: Look at the stdout and ps to make sure the process is gone.