5:52 p.m.
Paul Robinson created JBTM-1051:
-----------------------------------
Summary: 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: Amos Feng
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
5:52 p.m.
[
https://issues.jboss.org/browse/JBTM-1051?page=com.atlassian.jira.plugin....
]
Paul Robinson reassigned JBTM-1051:
-----------------------------------
Assignee: Paul Robinson (was: Amos Feng)
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
5:52 p.m.
[
https://issues.jboss.org/browse/JBTM-1051?page=com.atlassian.jira.plugin....
]
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/...
and
https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/...
# 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
5:54 p.m.
[
https://issues.jboss.org/browse/JBTM-1051?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1051:
-------------------------------------
A better solution would be to have this problem detected in the AS7 testsuite. This would
prevent the error from even being accepted into the AS7 codebase.
Ivo, can this type of check be made in the allTests junit suite?
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
6:18 p.m.
[
https://issues.jboss.org/browse/JBTM-1051?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1051:
-------------------------------------
I would add that I believe this issue can be (not formally, but effectively) resolved
through education.
Who ever makes a change to src/main/resources/standalone/configuration/*xml should be made
aware that they should also update src/main/resources/docs/examples/config/*xml
This issue should affect:
./messaging/src/test/resources/standalone-with-messaging.xml
./modcluster/src/test/resources/standalonemodcluster.xml
./build/src/main/resources/docs/examples/configs/standalone-hornetq-colocated.xml
./build/src/main/resources/docs/examples/configs/standalone-xts.xml
./build/src/main/resources/docs/examples/configs/standalone-minimalistic.xml
./build/src/main/resources/docs/examples/configs/standalone-jts.xml
./build/src/main/resources/docs/examples/configs/standalone-osgi-only.xml
So I see it as broader than XTS.
That said, +1 on checking whether the testsuite can detect it, but I don't know if the
other configs are tested during testsuite.
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
6:20 p.m.
[
https://issues.jboss.org/browse/JBTM-1051?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1051:
-------------------------------------
PS, shouldn't this issue be moved to an AS7 Jira?
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
6:36 p.m.
[
https://issues.jboss.org/browse/JBTM-1051?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1051:
-------------------------------------
I agree that education should help, but we will always need something in place to make
sure nothing slips through.
I also agree that the problem is broader than just XTS. However, I need something in place
ASAP that works for XTS. My fear would be that making it work for all configs would delay
this. We could do standalone-jts.xml as well, as we know how to detect when this one falls
out of sync.
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
6:49 p.m.
[
https://issues.jboss.org/browse/JBTM-1051?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1051:
-------------------------------------
I don't even know where standalone-jts.xml is referenced from :)
In my quickstarts I show people how to change the config manually. I wonder who added the
jts one?
Maybe that is an option for XTS? Explain the manual configuration?
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
9:18 p.m.
[
https://issues.jboss.org/browse/JBTM-1051?page=com.atlassian.jira.plugin....
]
Ivo Studensky commented on JBTM-1051:
-------------------------------------
Paul,
my XTS simple tests from JBQA-5839 have already been merged to AS7 testsuite as a part of
-DallTests. These tests use standalone-xts.xml configuration file and so should detect
whether AS7 is able to start up with this conf file or not. IMO from Transaction
team's point of view this could be satisfying for the moment.
Another thing is that all those additional configuration files from examples directory are
worth testing. I will ask Rajesh if it is on the QE plan.
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
3:59 p.m.
[
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
6:14 p.m.
[
https://issues.jboss.org/browse/JBTM-1051?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1051:
-------------------------------------
In fact, we are in the situation now where a change has been made to standalone-full.xml
and not standalone-xts.xml. It doesn't cause any errors at boot and, I is not breaking
XTS (as your tests must have passed).
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
6:49 p.m.
[
https://issues.jboss.org/browse/JBTM-1051?page=com.atlassian.jira.plugin....
]
Ivo Studensky commented on JBTM-1051:
-------------------------------------
You are right, Paul. A minor change in configuration does not have to be identified by
these tests. That is why I asked Rajesh for general testing of the configuration files. I
am still waiting for response.
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
6:06 p.m.
[
https://issues.jboss.org/browse/JBTM-1051?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1051:
-------------------------------------
Can this be moved to an AS7 Jira?
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
5:56 p.m.
[
https://issues.jboss.org/browse/JBTM-1051?page=com.atlassian.jira.plugin....
]
Paul Robinson commented on JBTM-1051:
-------------------------------------
Mostly fixed by https://issues.jboss.org/browse/AS7-3806. Although we do have a similar
issue if the templates for standalone-xts.xml and standalone-full.xml fall out of sync.
However, this should happen much less frequently.
https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/...
https://github.com/jbossas/jboss-as/blob/master/build/src/main/resources/...
I think we should resolve this issue as "won't fix" for now and then re-open
if the these templates fall out of sync.
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
6:04 p.m.
[
https://issues.jboss.org/browse/JBTM-1051?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1051:
-------------------------------------
Sure, but can we re-open issues like this in AS7 project do you think?
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
8:44 p.m.
[
https://issues.jboss.org/browse/JBTM-1051?page=com.atlassian.jira.plugin....
]
Tom Jenkinson closed JBTM-1051.
-------------------------------
Fix Version/s: (was: 5.0.0.M2)
Resolution: Deferred
Defering until we have issues with the templates again, subsequent issues will be raised
in AS7 Jira
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
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
4431
days inactive
4474
days old
jbossts-issues@lists.jboss.org
15 comments
3 participants
participants (3)
-
Ivo Studensky (JIRA) -
Paul Robinson (JIRA)
-
Tom Jenkinson (JIRA)