[ 
https://issues.apache.org/jira/browse/ARTEMIS-2855?focusedWorklogId=464196&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-464196
 ]

ASF GitHub Bot logged work on ARTEMIS-2855:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 29/Jul/20 17:46
            Start Date: 29/Jul/20 17:46
    Worklog Time Spent: 10m 
      Work Description: asfgit closed pull request #3225:
URL: https://github.com/apache/activemq-artemis/pull/3225


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 464196)
    Time Spent: 20m  (was: 10m)

> Define a new broker plugin to track XA transactions
> ---------------------------------------------------
>
>                 Key: ARTEMIS-2855
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2855
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>            Reporter: Domenico Francesco Bruscino
>            Assignee: Domenico Francesco Bruscino
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The broker is frequently used in transactions from the Wildfly/EAP app 
> server, acting as an XAResource manager to the app server's Transaction 
> Manager. In distributed environments, multiple app server instances can be 
> communicating to the same broker.
> It is common for these app servers to be incorrectly configured, using a 
> shared default nodeId, when this value is required to be unique for safe 
> operation. App server instances don't necessarily communicate peer to peer, 
> so can't detect this situation. The broker, however, sees nodeId values from 
> all its app server clients, so can detect this.
> Defining a new broker plugin interface to track XA transactions would allow 
> to implement an external plugin to detect the XA client misconfiguration.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to