#### Description of problem: EAP 6 documentation[1] says process-id mechanism can be changed from process-id-uuid to process-id-socket-binding. But it's impossible. [1] https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.1/html/Administration_and_Configuration_Guide/chap-Transaction_Subsystem.html#Configure_the_Transaction_Manager1 #### Steps to Reproduce: 1. Start EAP 6 ~~~ ./bin/standalone.sh ~~~ 2. Execute 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) ~~~ 3. Restart EAP 6 #### Actual results: The following ERROR occurred at JBoss start-up: ~~~ 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" ~~~ #### Expected results: JBoss starts without ERROR.
patch looks good to me
We have had a report that it may not work in all circumstances, just trying to verify the report before we raise PRs.
Although the patch functionally works with respect to the transaction manager, when the server is restarted and the config is read: /subsystem=transactions:read-resource(recursive=true) process-id-uuid returns undefined rather than false Similarly process-id-socket-process-id returns undefined rather than false It should be possible to make these settings persistent booleans. Thanks for the contribution so far, if you know how to report these values as false I am very happy to go with that solution.
*** Bug 1017816 has been marked as a duplicate of this bug. ***
Just a note: This bug was created for EAP 6.1.1 but this issue resides in 6.2.0 as well.
The root reason is it does not check the PROCESS_ID_UUID if defined when booting the coreEnvironment service in TransactionSubsytemAdd.
Verified for EAP 6.3.0.ER2. The process id generation by socket binding is possible to set in configuration.
do not think the bug had a measurable impact on EAP.