[JBoss JIRA] (JBTM-933) Compress the EIS name in the bqual
by Tom Jenkinson (Created) (JIRA)
Compress the EIS name in the bqual
----------------------------------
Key: JBTM-933
URL: https://issues.jboss.org/browse/JBTM-933
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Tom Jenkinson
Fix For: 4.15.4
Current most of the bqual is consumed by the EIS name (stored uncompressed) leaving little space for future enhancements. This was OK before, but there is potentially a requirement to use some of the bqual to store a node identifier (which, in the gtrid is able to be 36 bytes long).
Jonathan has pointed out that we can maintain a file somewhere where the user passes us an EIS name of say "foo" and we can add this to the file as integer 1, and so on. This file can be reloaded at startup into a hashmap so that we can still print out the real EIS name even though the XID bqual would only consume 4 bytes now.
--
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
12 years, 4 months
- 5
- 6
[JBoss JIRA] (JBTM-967) MBeans corresponding to XA resource log records do not expose the Jndi name of datasources
by Michael Musgrove (Created) (JIRA)
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.15.4
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
12 years, 4 months
- 2
- 1