[jboss-jira] [JBoss JIRA] (WFCORE-359) Failure to start the JVM should trigger a management update plan to rollback

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry moved WFLY-744 to WFCORE-359:
----------------------------------------------

          Project: WildFly Core  (was: WildFly)
              Key: WFCORE-359  (was: WFLY-744)
      Component/s: Domain Management
                       (was: Domain Management)
    Fix Version/s:     (was: Awaiting Volunteers)


> Failure to start the JVM should trigger a management update plan to rollback
> ----------------------------------------------------------------------------
>
>                 Key: WFCORE-359
>                 URL: https://issues.jboss.org/browse/WFCORE-359
>             Project: WildFly Core
>          Issue Type: Task
>          Components: Domain Management
>            Reporter: Andrig Miller
>
> I have come across situations where certain JVM options, typically related to NUMA options, can cause the JVM to segfault.  With our domain model, we expose the ability to set the JVM options, so I think this certainly would be a possibility.
> So, as we discussed on the Andiamo call today, this type of situation should cause a rollback of the management update plan, if the JVM fails to start.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)