[jbossts-issues] [JBoss JIRA] (JBTM-1051) Detect when standalone-xts.xml falls out of sync

Paul Robinson (JIRA) jira-events at lists.jboss.org
Mon Feb 6 03:52:51 EST 2012

    [ https://issues.jboss.org/browse/JBTM-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664366#comment-12664366 ] 

Paul Robinson commented on JBTM-1051:

One solution could be to use a CI job that: 

# Takes the last successful build of AS7
# Diffs https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/standalone/configuration/standalone-full.xml and https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/docs/examples/configs/standalone-xts.xml
# Excludes the expected changes from the output
# Fails the test if any remaining diffs occur.

The problem with this approach is that the ball is on our court, to fix the problem, and XTS is broken until we can have our pull request accepted.
> 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


More information about the jbossts-issues mailing list