Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-523

wildfly-init-redhat.sh should touch /var/lock/subsys/wildfly for properly shutdown

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 1.0.0.Alpha17
    • 1.0.0.Alpha16
    • Scripts
    • None

    Description

      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.

      Attachments

        Activity

          People

            tomazcerar Tomaž Cerar (Inactive)
            xkylex Kohei Nozaki (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: