Unable to change process-id mechanism from process-id-uuid to process-id-socket-binding on transaction subsystem in EAP 6

Issue

As EAP 6 documentation¹ says the following, it looks process-id mechanism can be changed from process-id-uuid to process-id-socket-binding:

Option	Description	CLI Command
process-id-uuid	Set to true to use the process identifier to create a unique identifier for each transaction. Otherwise, the socket-based mechanism is used. Defaults to true. Refer to process-id-socket-max-ports for more information.	/profile=default/subsystem=transactions/:write-attribute(name=process-id-uuid,value=true)

However, I tried the following CLI to change process-id mechanism:

/socket-binding-group=standard-sockets/socket-binding=txn-socket-process-id/:add(port=4714)
/subsystem=transactions:write-attribute(name=process-id-uuid,value=false)
/subsystem=transactions:write-attribute(name=process-id-socket-binding,value=txn-socket-process-id)

Apparently, configuration was changed successfully:

        <subsystem xmlns="urn:jboss:domain:transactions:1.3">
            <core-environment>
                <process-id>
                    <socket socket-binding="txn-socket-process-id"/>
                </process-id>
            </core-environment>
            ...
        </subsystem>

    ...

    <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
        ...
        <socket-binding name="txn-socket-process-id" port="4714"/>
        ...
    </socket-binding-group>

But JBoss start-up failed with the following ERROR occurred:

ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 44) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: "JBAS014746: process-id-uuid may not be null"

...(snip)...

INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.txn.ArjunaObjectStoreEnvironment (missing) dependents: [service jboss.txn.ArjunaRecoveryManager]
      service jboss.txn.ArjunaTransactionManager (missing) dependents: [service jboss.connector.bootstrapcontext.default]
      service jboss.txn.CoreEnvironment (missing) dependents: [service jboss.txn.ArjunaRecoveryManager, service jboss.ejb.tx-recovery-service]
      service jboss.txn.JTAEnvironment (missing) dependents: [service jboss.txn.ArjunaRecoveryManager]
      service jboss.txn.TransactionManager (missing) dependents: [service jboss.ejb3.timerService.fileTimerPersistence, service jboss.ejb.utilities, service jboss.ejb.remote-transactions-repository, service jboss.connector.transactionintegration, JBAS014799: ... and 3 more ]
      service jboss.txn.TransactionSynchronizationRegistry (missing) dependents: [service jboss.ejb3.timerService.fileTimerPersistence, service jboss.ejb.utilities, service jboss.connector.transactionintegration, service jboss.jpa, JBAS014799: ... and 2 more ]
      service jboss.txn.UserTransaction (missing) dependents: [service jboss.ejb.utilities, service jboss.ejb.remote-transactions-repository]
      service jboss.txn.UserTransactionRegistry (missing) dependents: [service jboss.jpa-usertransactionlistener, service jboss.connector.transactionintegration]

...(snip)...

ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) started (with errors) in 3332ms - Started 250 of 351 services (27 services failed or missing dependencies, 73 services are passive or on-demand)