Description of problem: If the rhq-server.properties file is missing the property rhq.server.log-level, the JBoss ON server fails to start: JBAS014802: Cannot resolve expression 'expression "${rhq.server.log-level}"' -- java.lang.IllegalStateException: Failed to resolve expression: ${rhq.server.log-level} at org.rhq.common.jbossas.client.controller.LoggingJBossASClient.setLoggerLevel(LoggingJBossASClient.java:92) [rhq-jboss-as-dmr-client-4.9.0.JON320GA.jar:4.9.0.JON320GA] This is common when upgrading from a previous version of JBoss ON that did not use this property. As with any property definition, a reasonable default should be used. In this case, the default seems to be INFO so it would make sense that the property expression use INFO as its default value and that this not be dependent on the rhq-server.properties file itself. Version-Release number of selected component (if applicable): 3.2.0 How reproducible: Always Steps to Reproduce: 1. Extract JBoss ON 3.2 server archive. 2. Set server bind address in rhq-server.properties. 3. Remove rhq.server.log-level property from rhq-server.properties file. 4. Run install: rhqctl install Actual results: Install will fail with error: 14:52:59,380 ERROR [org.rhq.enterprise.server.installer.Installer] The installer will now exit due to previous errors: org.rhq.common.jbossas.client.controller.FailureException: Failed request: JBAS014802: Cannot resolve expression 'expression "${rhq.server.log-level}"' -- java.lang.IllegalStateException: Failed to resolve expression: ${rhq.server.log-level} at org.rhq.common.jbossas.client.controller.LoggingJBossASClient.setLoggerLevel(LoggingJBossASClient.java:92) [rhq-jboss-as-dmr-client-4.9.0.JON320GA.jar:4.9.0.JON320GA] at org.rhq.enterprise.server.installer.ServerInstallUtil.configureLogging(ServerInstallUtil.java:187) [rhq-installer-util-4.9.0.JON320GA.jar:4.9.0.JON320GA] at org.rhq.enterprise.server.installer.InstallerServiceImpl.install(InstallerServiceImpl.java:333) [rhq-installer-util-4.9.0.JON320GA.jar:4.9.0.JON320GA] at org.rhq.enterprise.server.installer.Installer.doInstall(Installer.java:116) [rhq-installer-util-4.9.0.JON320GA.jar:4.9.0.JON320GA] at org.rhq.enterprise.server.installer.Installer.main(Installer.java:57) [rhq-installer-util-4.9.0.JON320GA.jar:4.9.0.JON320GA] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_05] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_05] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_05] at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_05] at org.jboss.modules.Module.run(Module.java:270) [jboss-modules.jar:1.2.2.Final-redhat-1] at org.jboss.modules.Main.main(Main.java:411) [jboss-modules.jar:1.2.2.Final-redhat-1] Expected results: Install should succeed with no error.
*** Bug 1080507 has been marked as a duplicate of this bug. ***
git commit to master: 0209557a16a9fc7ddb5a55a4faa055c352ff8d32 git commit to release/jon3.2.x: 0c56f68d2b6437a30f2b37829534c10321735f9a If you run the installer without having rhq.server.log-level set in rhq-server.properties, the installation will now succeed.
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993
Verified on Version : 3.3.0.DR01 Build Number : 6468454:dda0a47
Looks good. Except I changed "JBoss Server" to "JON Server" since we don't need to explicitly say its a JBoss AS Server under the covers. Its just "the JON Server" to users. Anyway, the "Doc Text" field looks good to me.