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

Shutdown on startup error

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Unresolved
    • Major
    • None
    • None
    • Management
    • None

    Description

      Currently WildFly starts and up running although it got critical errors during boot.

      For example, 8080 port is being used by the other process and undertow subsystem was not functioning, transaction manager and logging subsystems are failed to boot due to file permission error, or someone started the instance twice by mistake.

      It would be nice if we can have an option to trigger shutdown the non-healthy instance in these boot error situations, for subsystem level errors and for deployment errors.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              rhn-support-tkimura Takayoshi Kimura
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: