[jboss-jira] [JBoss JIRA] (WFLY-2623) Unable to change process-id mechanism from process-id-uuid to process-id-socket-binding on transaction
RH Bugzilla Integration (JIRA)
issues at jboss.org
Wed Apr 23 04:50:35 EDT 2014
[ https://issues.jboss.org/browse/WFLY-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12963192#comment-12963192 ]
RH Bugzilla Integration commented on WFLY-2623:
-----------------------------------------------
Ondrej Chaloupka <ochaloup at redhat.com> changed the Status of [bug 1036739|https://bugzilla.redhat.com/show_bug.cgi?id=1036739] from ON_QA to VERIFIED
> 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
> Security Level: Public(Everyone can see)
> Components: Transactions
> Affects Versions: 8.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list