[jboss-jira] [JBoss JIRA] Updated: (AS7-483) Failure to start the JVM should trigger a management update plan to rollback

[Jason Greene (JIRA)]

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

Jason Greene updated AS7-483:
-----------------------------

    Fix Version/s: 7.1.0.Beta1
                       (was: 7.1.0.Alpha1)


> Failure to start the JVM should trigger a management update plan to rollback
> ----------------------------------------------------------------------------
>
>                 Key: AS7-483
>                 URL: https://issues.jboss.org/browse/AS7-483
>             Project: Application Server 7
>          Issue Type: Task
>          Components: Domain Management
>    Affects Versions: 7.0.0.Alpha1
>            Reporter: Andrig Miller
>             Fix For: 7.1.0.Beta1
>
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira