[
https://issues.jboss.org/browse/JBTM-1051?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1051:
-------------------------------------
Ivo,
Of course, I forgot these tests would do this also. Do your tests fail if the server boots
with errors, even though XTS is still functioning correctly?
We still have the problem where a minor change is forgotten; one which doesn't break
XTS and doesn't fail the server boot. However, these are relatively minor and could
probably be checked manually every now and then.
Detect when standalone-xts.xml falls out of sync
------------------------------------------------
Key: JBTM-1051
URL:
https://issues.jboss.org/browse/JBTM-1051
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 5.0.0.M2
We've been having a problem with updates being made to standalone-full.xml and not
being applied to standalone-xts.xml. Most of the time this causes no obvious problem to
us, but clearly will cause a problem for our users. If they try to use XTS in conjunction
with some other technology, such as JMS, that requires a change to the server config, they
will hit problems. However, other times this problem is more obvious as it can prevent the
AS from booting or produce errors.
In the long term, we aim to have a better solution to this multiple server config issue.
In the short term we need to detect when these files fall out of sync and then create a
pull request to fix it.
On failure of the job, we can then fix it manually by:
# Overwriting standalone-xts.xml with standalone-full.xml.
# Adding the '<extension module="org.jboss.as.xts"/>' line back
in
# Adding the '<subsystem xmlns="urn:jboss:domain:xts:1.0">' block
back in.
# Jira the problem in the AS7 jira project and name the issue "standalone-xts.xml
fallen out of sync with standalone-full.xml" (Essential for demonstrating to the AS7
team that this is a problem)
# Create a pull request to resolve the issue.
We need an automated way of detecting this problem, so that it can be fixed ASAP.
--
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