System properties configured in the server group or server level are not added in JBoss EAP 6.4 CP3 (6.4.3)

Environment

• Red Hat JBoss Enterprise Application Platform (EAP)
  • 6.4 CP03

Issue

• After applying the CP03 patch in the JBoss EAP 6.4, all system properties that should be loaded on JBoss boot that are configured in the server groups or server level are not read. Only the global system properties that are configured to the Domain are loaded.
• We patch our jBoss EAP 6.4.1 to 6.4.3 and found that the system properties are not set when starting up the server.Then properties are set in both server group configuration and on server configuration level. None of the system properties are set when booting the server.
• System properties defined in domain configuration not available to deployed java code in domain mode.
• We have used jboss.tx.node.id parameter in each server for transaction. it was working properly. After updating jboss version to 6.4.3 from 6.4.2. the error occured when starting servers.
• During server start it cannot read system properties. Error message is following: "JBAS014802: Cannot resolve expression '${crx.mq.user}". But "crx.mq.user" property available here: Go to Domain tab --> Server Configurations section --> Click any server --> Check System Properties tab.

Resolution

• Update to EAP 6.4CP04 or later.
• Alternatively, a patch was released for the This content is not included.6.4.3 ZIP, This content is not included.RHEL7 RPM, RHEL6 RPM, and RHEL5 RPM distributions. Red Hat recommends that all customers using JBoss EAP 6.4 update 03 (6.4.3) apply this patch.

Root Cause

This content is not included.Bug 1257301 covers this issue.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.