August 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1801) Move all test properties into root pom.xml

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1801?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1801: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.M4) > Move all test properties into root pom.xml > ------------------------------------------ > > Key: JBTM-1801 > URL: https://issues.jboss.org/browse/JBTM-1801 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Trivial > Fix For: 5.0.0.M5 > > > We have these test properties duplicated in many places: > https://github.com/jbosstm/narayana/blob/master/XTS/localjunit/pom.xml#L22 > We should move them up to the root pom.xml to simplify maintenance. As part of this task you need to hunt out all these usages and similar. Then come up with a common set of properties that works in all cases and move to the root pom.xml. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1750) Create Quickstarts for REST-AT bridge

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1750?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1750: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.M4) > Create Quickstarts for REST-AT bridge > ------------------------------------- > > Key: JBTM-1750 > URL: https://issues.jboss.org/browse/JBTM-1750 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Demonstrator, REST > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M5 > > Original Estimate: 3 hours > Time Spent: 7 hours, 30 minutes > Remaining Estimate: 0 minutes > > We should take the ones from Gytis' dissertation and bring them up to the standard of the existing ones (Which they may already be). and then merge into our quickstart repo. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1482) If a naughty afterCompletion sync throws an exception, log the exception call stack

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1482?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1482: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.M4) > If a naughty afterCompletion sync throws an exception, log the exception call stack > ----------------------------------------------------------------------------------- > > Key: JBTM-1482 > URL: https://issues.jboss.org/browse/JBTM-1482 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Scott Marlow > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.0.0.M5 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Currently, when this happens with AS, I see: > {quote} > 2013-02-18 16:24:43,837|WARN |[com.arjuna.ats.jta]|(ThreadId: Transaction Reaper Worker 221)|ARJUNA016029: SynchronizationImple.afterCompletion - failed for org.jboss.as.jpa.transaction.TransactionUtil$SessionSynchronization@634ef5a7 with exception: java.lang.NullPointerException > {quote} > From a related email conversation: > {quote} > Here's our Logger code: > @Message(id = 16029, value = "SynchronizationImple.afterCompletion - failed for {0} with exception", format = MESSAGE_FORMAT) > @LogMessage(level = WARN) > public void warn_resources_arjunacore_SynchronizationImple(String arg0, @Cause() Throwable arg1); > Here is where we call our logger: > jtaLogger.i18NLogger.warn_resources_arjunacore_SynchronizationImple(_theSynch.toString(), e); > Maybe the message should have the {1} in it, i.e. it change it like so: > "SynchronizationImple.afterCompletion - failed for {0} with exception {1}" > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1718) Resolve the ParticipantCompletion race condition

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1718?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1718: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.M4) > Resolve the ParticipantCompletion race condition > ------------------------------------------------ > > Key: JBTM-1718 > URL: https://issues.jboss.org/browse/JBTM-1718 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M5 > > > This issue is documented here: JBTM-1429 > In the documentation for JBTM-1429, we state that this issue is unlikely to happen in a distributed environment. This is true, however, the Compensations API is designed to work local-only as well as distributed over WS-BA. Therefore it is much more likely to happen in a production environment. > Therefore we need to remove this race condition. It can be done in a proprietary mannor as we are not interoperating with another implementation ion local-only mode. When distributing the transaction we fall back to the standard protocol that is susceptible to the race condition. However, as we stated in the docs, this condition is unlikely to manifest in a distributed environment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1802) Consider moving Arquillian profiles to root pom.xml

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1802?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1802: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.M4) > Consider moving Arquillian profiles to root pom.xml > --------------------------------------------------- > > Key: JBTM-1802 > URL: https://issues.jboss.org/browse/JBTM-1802 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System, Testing > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.M5 > > > We have three Arquillian profiles (for managed, remote and ipv6-managed) present in the pom of nearly every test that uses Arquillian. I suspect they can all be identical and thus placed int he root pom.xml. This should simplify maintenance and will ensure any fixes to this config are made throughout. > The problem is that we may have legitimate reasons for this config to differ for some tests. Maybe we could use overrides in these cases. > Assigning to Tom for his input. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1749) Failure building Javadoc when JAVA_HOME is empty

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1749?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1749: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.M4) > Failure building Javadoc when JAVA_HOME is empty > ------------------------------------------------ > > Key: JBTM-1749 > URL: https://issues.jboss.org/browse/JBTM-1749 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Environment: See discussion > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.M5 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > To reproduce: > # export JAVA_HOME= > # /opt/apache-maven-3.0.5/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml > It also happens if you use the maven version in tools/maven (also version 3.0.5). > This doesn't fail: > # export JAVA_HOME= > # /opt/apache-maven-3.0.3/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml > Currently only seen this on a Mac. Would be good if a linux user could try to reproduce. > Maven 3.0.5 is the latest release. I've not found a known issue for this, but it is hard to search for. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1873) Create quickstart showing new features implemented with @Compensatable

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1873?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1873: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.M4) > Create quickstart showing new features implemented with @Compensatable > ---------------------------------------------------------------------- > > Key: JBTM-1873 > URL: https://issues.jboss.org/browse/JBTM-1873 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator, TXFramework, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.M5 > > Original Estimate: 4 hours > Time Spent: 3 hours > Remaining Estimate: 1 hour > > Show main features provided by @Compensatable annotation: dontCancelOn, cancelOn, compensation types. > Reuse Paul's quickstart JBTM-1682. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1716) BACoordinatorCompletionTest test hung

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1716?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1716: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.M4) > BACoordinatorCompletionTest test hung > ------------------------------------- > > Key: JBTM-1716 > URL: https://issues.jboss.org/browse/JBTM-1716 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Trivial > Fix For: 5.0.0.M5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > org.jboss.narayana.txframework.functional.ws.ba.coordinatorCompletion.BACoordinatorCompletionTest test hung. > See here for log: http://172.17.131.2/job/narayana/TESTS=XTS,jdk=jdk7.latest,label=linux/63... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1862) C++ XATMI Implementation tests crashed

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1862?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1862: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.M4) > C++ XATMI Implementation tests crashed > -------------------------------------- > > Key: JBTM-1862 > URL: https://issues.jboss.org/browse/JBTM-1862 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.M5 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/205/TESTS=BLACKTI... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1804: -------------------------------- Fix Version/s: 5.0.0.M5 (was: 5.0.0.M4) > JTS remote tests not run and no code coverage > --------------------------------------------- > > Key: JBTM-1804 > URL: https://issues.jboss.org/browse/JBTM-1804 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS, Testing > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Amos Feng > Fix For: 5.0.0.M5 > > > The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build. > It would then be beneficial to have them instrumented by emma to get code coverage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2013