[jboss-jira] [JBoss JIRA] (WFCORE-230) Failure by ProcessController to launch a server vm is not logged

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018420#comment-13018420 ] 

Brian Stansberry commented on WFCORE-230:
-----------------------------------------

DefaultJvmUtils is detecting this and throwing an exception on the HC, during execution of ManagedServer.ProcessAddTask. But ManagedServer.internalSetState is catching the exception and logging it at DEBUG.

Simplest fix would be to change that log level to ERROR, but I'll need to check with Emanuel re: the thinking behind using debug there and in other spots in ManagedServer.

> Failure by ProcessController to launch a server vm is not logged
> ----------------------------------------------------------------
>
>                 Key: WFCORE-230
>                 URL: https://issues.jboss.org/browse/WFCORE-230
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 1.0.0.Alpha11
>            Reporter: Brian Stansberry
>             Fix For: 1.0.0.CR1
>
>
> In a domain configuration, if a server is associated with an incorrectly configurated jvm java-home (e.g. domain.xml -> server-groups -> jvm), it will fail silently (no error shown in logs). For example:
> ```
> <server-group name="mySrvrGrp" profile="full">
>   <jvm name="my-default" java-home="/usr/java/wrongPath">
>     <heap size="1024m" max-size="4096m"/>
>     <permgen size="256m" max-size="256m"/>
>     <stack size="256k"/>
> ```



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