[jboss-jira] [JBoss JIRA] (WFLY-2623) Unable to change process-id mechanism from process-id-uuid to process-id-socket-binding on transaction
Harald Pehl (JIRA)
issues at jboss.org
Tue Aug 18 03:57:27 EDT 2015
[ https://issues.jboss.org/browse/WFLY-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harald Pehl reopened WFLY-2623:
-------------------------------
Works on WildFly 8.2, but fails on WildFly 9.x and latest WildFly 10.0.0.Beta2-SNAPSHOT.
After creating the following socket binding
{code}
[standalone at localhost:9990 /] /socket-binding-group=standard-sockets/socket-binding=txn-socket-process-id:add(port=4714)
{"outcome" => "success"}
{code}
any combination to change process-id mechanism from process-id-uuid to process-id-socket-binding fails:
{code:title=Batch / Order 1}
[standalone at localhost:9990 /] batch
[standalone at localhost:9990 / #] /subsystem=transactions:write-attribute(name=process-id-uuid,value=false)
[standalone at localhost:9990 / #] /subsystem=transactions:write-attribute(name=process-id-socket-binding,value=txn-socket-process-id)
[standalone at localhost:9990 / #] run-batch -v
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "WFLYCTL0105: process-id-uuid is invalid in combination with process-id-socket-binding"}}
{code}
{code:title=Batch / Order 2}
[standalone at localhost:9990 /] batch
[standalone at localhost:9990 / #] /subsystem=transactions:write-attribute(name=process-id-socket-binding,value=txn-socket-process-id)
[standalone at localhost:9990 / #] /subsystem=transactions:write-attribute(name=process-id-uuid,value=false)
[standalone at localhost:9990 / #] run-batch -v
The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error): {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "WFLYCTL0105: process-id-uuid is invalid in combination with process-id-socket-binding"}}
{code}
{code:title=Single Commands}
[standalone at localhost:9990 /] /subsystem=transactions:write-attribute(name=process-id-uuid,value=false)
{
"outcome" => "failed",
"failure-description" => "WFLYTX0025: Either process-id-uuid must be 'true' or process-id-socket-binding must be defined.",
"rolled-back" => true
}
[standalone at localhost:9990 /] /subsystem=transactions:write-attribute(name=process-id-socket-binding,value=txn-socket-process-id)
{
"outcome" => "failed",
"failure-description" => "WFLYCTL0105: process-id-uuid is invalid in combination with process-id-socket-binding",
"rolled-back" => true
}
{code}
> Unable to change process-id mechanism from process-id-uuid to process-id-socket-binding on transaction
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-2623
> URL: https://issues.jboss.org/browse/WFLY-2623
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 10.0.0.Beta1
> Reporter: Amos Feng
> Assignee: Hayk Hovsepyan
> Labels: transaction
> Fix For: 8.0.0.Final
>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1036739
> process-id mechanism can not be changed from process-id-uuid to process-id-socket-binding.
> The following ERROR occurred at JBoss start-up:
> {noformat}
> 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"
> {noformat}
> The root reason is it does not check the PROCESS_ID_UUID if defined when booting the coreEnvironment service in TransactionSubsytemAdd.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list