]
Kabir Khan closed WFCORE-523.
-----------------------------
Fix Version/s: 1.0.0.Alpha17
Resolution: Done
wildfly-init-redhat.sh should touch /var/lock/subsys/wildfly for
properly shutdown
----------------------------------------------------------------------------------
Key: WFCORE-523
URL:
https://issues.jboss.org/browse/WFCORE-523
Project: WildFly Core
Issue Type: Enhancement
Components: Scripts
Affects Versions: 1.0.0.Alpha16
Environment: CentOS 6.6
Reporter: Kohei Nozaki
Assignee: Tomaz Cerar
Fix For: 1.0.0.Alpha17
When I shutdown CentOS, it doesn't wait for complete shutdown of WildFly. I see that
server.log doesn't end with `JBAS015950: WildFly 8.2.0.Final "Tweek" stopped
in 437ms` at shutdown of CentOS. also there's no message which indicates that
processing of WildFly shutdown (e.g. Stopping wildfly...). it seems like that shutdown
script was not invoked and CentOS killed the process of WildFly.
It's not good for embedded database that requires shutdown properly. I have a
embedded Derby within WildFly and it needs properly shutdown for every time to avoid data
corruption.