[jbossts-issues] [JBoss JIRA] (JBTM-967) MBeans corresponding to XA resource log records do not expose the Jndi name of datasources
[
https://issues.jboss.org/browse/JBTM-967?page=com.atlassian.jira.plugin.s...
]
Michael Musgrove resolved JBTM-967.
-----------------------------------
Resolution: Done
Works with JTA but for JTS we only provide best effort support for JNDI resource names
(the code uses reflection to check whether the XAResource log record has the relevant
methods). Full support for the requirement may require an update to ArjunaOTS.idl.
Note that JBTM-895 is introduced distributed transaction support over JTA. It may be
possible to provide some information via that protocol.
MBeans corresponding to XA resource log records do not expose the
Jndi name of datasources
------------------------------------------------------------------------------------------
Key: JBTM-967
URL: https://issues.jboss.org/browse/JBTM-967
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Tooling
Affects Versions: 4.15.3
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 4.16.0.Beta1
XA resource records now encode the Jndi name of datasources. This information needs to be
reflected in the MBeans that represent these records.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira