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

[David Lloyd (Updated) (JIRA)]

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

David Lloyd updated AS7-483:
----------------------------

    Fix Version/s: Open To Community
                       (was: 7.1.0.Beta1)

    
> 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: Open To Community
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira