[jboss-jira] [JBoss JIRA] (WFLY-2623) Unable to change process-id mechanism from process-id-uuid to process-id-socket-binding on transaction

[Ondřej Chaloupka (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099681#comment-13099681 ] 

Ondřej Chaloupka edited comment on WFLY-2623 at 8/19/15 3:27 AM:
-----------------------------------------------------------------

If I can I would vote for the third option. It seems to me the most meaningful.

One operation that I'm aware of is the {{enable}} and {{disable}} operation on datasource. Maybe it could be inspiration (in case, not sure).

{code}
/subsystem=datasources/data-source=ExampleDS:enable()
/subsystem=datasources/data-source=ExampleDS:disable()
{code}

Then there is attribute {{/subsystem=datasources/data-source=ExampleDS:read-attribute(name=enabled)}} which shows the actual value. That attribute should be read-only as Harald mentioned. Thought the enable thing could not be the best example as Stefano plans to remove those operations (WFLY-4294, WFLY-4050)

{code}
/subsystem=datasources/data-source=ExampleDS:read-operation-description(name=enable)
/subsystem=datasources/data-source=ExampleDS:read-resource-description()
{code}


was (Author: ochaloup):
If I can I would vote for the third option. It seems to me the most meaningful.

One operation that I'm aware of is the {{enable}} and {{disable}} operation on datasource. Maybe it could be inspiration (in case, not sure).

{code}
/subsystem=datasources/data-source=ExampleDS:enable()
/subsystem=datasources/data-source=ExampleDS:disable()
{code}

Then there is attribute {{/subsystem=datasources/data-source=ExampleDS:read-attribute(name=enabled)}} which shows the actual value. That attribute should be read-only as Harald mentioned. Thought the enable thing could not be the best example as Stefano plan to remove those operations (WFLY-4294, WFLY-4050)

{code}
/subsystem=datasources/data-source=ExampleDS:read-operation-description(name=enable)
/subsystem=datasources/data-source=ExampleDS:read-resource-description()
{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
>            Priority: Critical
>              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)