Log statements in process-controller logs when wrong JVM settings are configured in JBoss EAP 6.

Solution Verified - Updated -

Issue

  • There are cases when customers or operators configure wrong JVM settings. For example, Configure the following in domain.xml under server-groups:
    <server-groups>
        <server-group name="server-group-1" profile="default">
            <jvm name="default" java-home="/opt/jet/java/jdk1.8.0-x64">
                <heap max-size="256m"/>
                <jvm-options>
                    <option value="-server"/>
                    <option value="-verbose:gc"/>
                    <option value="-XX:+DisableExplicitGC"/>
                    <option value="-XX:+PrintGCDateStamps"/>
                    <option value="-XX:+PrintGCDetails"/>
                    <option value="-XX:+UseConcMarkSweepGC"/>
                    <option value="-XX:foo"/>
                </jvm-options>
            </jvm>

The option -XX:foo is wrong and as a result, servers inside server-group aren't started. The below message is logged in process-controller logs :

2016-02-18 14:20:46,232 [reaper for Server:server-1] INFO  org.jboss.as.process.Server:server-1.status - JBAS012010: Process 'Server:server-1' finished with an exit status of 1

There is no reason logged as to why the JVM failed to start. This always takes a long time to find out. Is there a way, how we can find out more about the cause?

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.