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

Solution Verified - Updated -

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.

Environment

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

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content