Description of problem:

This problem was discovered when testing updates to the instructions for the 'jts' quickstart. To reproduce the problem:

1. Open a terminal and navigate to the root of the JBoss EAP install directory.

2. Start the server with this command:

    $ bin/standalone.sh -c standalone-full.xml -Djboss.tx.node.id=node1

3. Open a new terminal, navigate to the root of the JBoss EAP install directory, and connect to the jboss-cli:

    $ bin/jboss-cli.sh --connect

4. Run the following commands:

    /subsystem=jacorb/:write-attribute(name=transactions,value=on)
    /subsystem=jacorb:write-attribute(name=name,value=${jboss.node.name})
    /subsystem=jacorb:write-attribute(name=root-context,value=${jboss.node.name}/Naming/root)

    /subsystem=transactions/:write-attribute(name=jts,value=true)
    /subsystem=transactions/:write-attribute(name=node-identifier,value=${jboss.tx.node.id})

The commands run successfully. Stop the server and open the standalone-full.xml configuration file. You see the following in the transactions subsystem:

    <core-environment node-identifier="$">

The server was started with the argument '-Djboss.tx.node.id=node1' so the resulting configuration should be:

    <core-environment node-identifier="node1">
 
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: