I have a weird situaion in my setup where the AEM Publish (6.5.8) stopped on its own. The AEM publish on RH linux (AWS EC2 instance) stopped on its own while no one had triggered any command. the GC logs dont say much but the thread dump and memory heap dump frm underlying JVM was not available from loggers.
the error logs suggets it was a clean shutown as I could see [FelixShutdown] info messages started flowing in error log. Is there a condition written under which AEM service stops itself automatically ? later the start of the service was a clean start with no loss of any content or code of configuration. Looks like an issue with JVM.