Created attachment 991368 [details] server log excerpt Description of problem: Having a domain with a single server group and two eap hosts (all on localhost), following system property cause server to fail on startup: <property name="org.jbpm.designer.perspective" value="${org.jbpm.designer.perspective:full}"/> The problem occurs only in definition with possibility to override default value - <property name="X" value="${Y:default}"/>, where X = Y Please see the error message in attached server log excerpt. More interesting is the fact that the issue shows with domain mode only, standalone mode works with properties defined as above. Version-Release number of selected component (if applicable): 6.4.0.GA (version.txt)
EAP 6.3.0 domain starts without issues with such system property definition
I'm curious -- was this ever meant to in some situation resolve to something other than "full"? IOW, is this style or writing an expression anything other than a mistake?
s/style or writing/style of writing/g
It was supposed to use "full" as a default value, but the value can be override by defining the property at EAP startup, e.g. -Dorg.jbpm.designer.perspective=something_different Anyway, as had been said, there is a difference between 6.4 and 6.3 and for 6.4, even between standalone and domain. In case an expression like this is no longer supported, please make sure it's properly documented and server in standalone mode should fail fast as well as in domain mode.
EAP 6.3.0 <property name="org.jbpm.designer.perspective" value="${org.jbpm.designer.perspective:full}"/> [domain@localhost:9999 /] :resolve-expression-on-domain(expression="${org.jbpm.designer.perspective}") { "outcome" => "success", "result" => undefined, "server-groups" => {"main-server-group" => {"host" => {"master" => { "server-one" => {"response" => { "outcome" => "success", "result" => "${org.jbpm.designer.perspective:full}" }}, "server-two" => {"response" => { "outcome" => "success", "result" => "${org.jbpm.designer.perspective:full}" }} }}}} } <property name="org.jbpm.designer.perspective" value="${file.separator:full}"/> [domain@localhost:9999 /] :resolve-expression-on-domain(expression="${org.jbpm.designer.perspective}") { "outcome" => "success", "result" => undefined, "server-groups" => {"main-server-group" => {"host" => {"master" => { "server-one" => {"response" => { "outcome" => "success", "result" => "/" }}, "server-two" => {"response" => { "outcome" => "success", "result" => "/" }} }}}} } <property name="org.jbpm.designer.perspective" value="${foo:full}"/> [domain@localhost:9999 /] :resolve-expression-on-domain(expression="${org.jbpm.designer.perspective}") { "outcome" => "success", "result" => undefined, "server-groups" => {"main-server-group" => {"host" => {"master" => { "server-one" => {"response" => { "outcome" => "success", "result" => "full" }}, "server-two" => {"response" => { "outcome" => "success", "result" => "full" }} }}}} }
Another question: Where is this system property declared in the domain configuration? First level child of domain.xml? First le
domain -> system-properties -> property
Martin, The 6.3.0 behavior with value="${org.jbpm.designer.perspective:full}" looks incorrect as well, as the resolved value is not "full". Thanks, guys, for the info.
Should be fixed by DMR upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1192972
verified on EAP 6.4.0.ER3