Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1080507

Summary: Server fails to start if rhq.server.log-level is not explicitly defined in rhq-server.properties
Product: [JBoss] JBoss Operations Network Reporter: Larry O'Leary <loleary>
Component: UpgradeAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED DUPLICATE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: unspecified    
Version: JON 3.2CC: dsteigne
Target Milestone: ---   
Target Release: JON 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1078498 Environment:
Last Closed: 2014-03-28 21:44:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Larry O'Leary 2014-03-25 14:56:39 UTC
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.

Comment 1 Larry O'Leary 2014-03-28 21:44:23 UTC

*** This bug has been marked as a duplicate of bug 1080508 ***