[
https://issues.jboss.org/browse/JBTM-933?page=com.atlassian.jira.plugin.s...
]
Tom Jenkinson commented on JBTM-933:
------------------------------------
The main questions I have are:
1. where would this file be written to, is it ok to write to current working directory?
2. the XID would have this integer in its bqual, therefore, are there possibly none-TS
tools that would want to read the bqual and need to read meaningful information regarding
the EIS without the benefit of our utility classes?
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