September 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1341) Reject setting node identifier on CoreEnvironmentBean unless it can be successfully used by TxControl

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1341?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-1341: --------------------------------- For backport, I will do it but leaving assignee > Reject setting node identifier on CoreEnvironmentBean unless it can be successfully used by TxControl > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-1341 > URL: https://issues.jboss.org/browse/JBTM-1341 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M2 > > > It is too easy to miss the warning message. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1341) Reject setting node identifier on CoreEnvironmentBean unless it can be successfully used by TxControl

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1341?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1341: -------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/186, https://github.com/jbosstm/narayana/pull/726 (was: https://github.com/jbosstm/narayana/pull/186) > Reject setting node identifier on CoreEnvironmentBean unless it can be successfully used by TxControl > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-1341 > URL: https://issues.jboss.org/browse/JBTM-1341 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M2 > > > It is too easy to miss the warning message. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2055) Add testing on WELD container

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2055?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2055. ------------------------------- > Add testing on WELD container > ----------------------------- > > Key: JBTM-2055 > URL: https://issues.jboss.org/browse/JBTM-2055 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2150) Update narayana.sh and narayana-quickstarts/config to not require WILDFLY_MASTER_VERSION

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2150?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2150. ------------------------------- > Update narayana.sh and narayana-quickstarts/config to not require WILDFLY_MASTER_VERSION > ---------------------------------------------------------------------------------------- > > Key: JBTM-2150 > URL: https://issues.jboss.org/browse/JBTM-2150 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > They should be able to infer this from the projects own pom files. > For narayana.sh it is in /pom.xml: > <jboss-as.version>8.0.1.Final-SNAPSHOT</jboss-as.version> > For narayana-quickstart/config it is in (for example) ./XTS/wsat-jta-multi_service/pom.xml: > <jboss-as.version>8.0.1.Final-SNAPSHOT</jboss-as.version> -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1763) Consider running the QA tests in parrallel

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1763?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1763. ------------------------------- > Consider running the QA tests in parrallel > ------------------------------------------ > > Key: JBTM-1763 > URL: https://issues.jboss.org/browse/JBTM-1763 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Testing > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Priority: Minor > > The QA tests currently take 5hrs to run per orb. This constitutes 83% of our CI run time. > My understanding is that the time is mostly taken up in Thread.sleep. The test times range from 1 to 99seconds. So there are no major hotspots. The problem is that there are so many tests. > I suspect we could run these tests in parallel to make better utilisation of resources. > The tests don't run in an AS, but they do acquire ports. There may be other restrictions that make running them in parallel hard or impossible. > It would be easier to simply carve up the tests into, say 5 parts per orb and have CI do the parallelism. However, this will consume more CI nodes than if we ran them in parallel on a single node. > I think it would be worth investigating if we can run the tests in n batches (say n=10 initially, but should be configurable). Where each batch runs with a different port configuration. This may prove too disruptive to the tests, > and also more bother than it is worth. Maybe we could do an initial investigation to see if this has legs? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2182) [quickstart] NoClassDefFoundError on ArjunaJTA/maven

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2182?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2182. --------------------------------- Resolution: Done Resolved in https://github.com/jbosstm/quickstart/commit/daa819a176ade22ae75c1e05e127... > [quickstart] NoClassDefFoundError on ArjunaJTA/maven > ---------------------------------------------------- > > Key: JBTM-2182 > URL: https://issues.jboss.org/browse/JBTM-2182 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Andrew Rubinger > Assignee: Tom Jenkinson > Fix For: 5.0.4 > > > [INFO] --- exec-maven-plugin:1.2:exec (default-cli) @ maven --- > Exception in thread "main" java.lang.RuntimeException: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:81) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:49) > at com.arjuna.ats.jta.common.jtaPropertyManager.getJTAEnvironmentBean(jtaPropertyManager.java:42) > at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:71) > at TransactionManagerExample.main(TransactionManagerExample.java:39) > Caused by: java.lang.NoClassDefFoundError: Ljavax/transaction/TransactionManager; > at java.lang.Class.getDeclaredFields0(Native Method) > at java.lang.Class.privateGetDeclaredFields(Class.java:2570) > at java.lang.Class.getDeclaredFields(Class.java:1903) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.configureFromProperties(BeanPopulator.java:135) > at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:78) > ... 4 more > Caused by: java.lang.ClassNotFoundException: javax.transaction.TransactionManager > at java.net.URLClassLoader$1.run(URLClassLoader.java:372) > at java.net.URLClassLoader$1.run(URLClassLoader.java:361) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:360) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 9 more > Probably due to Tx API being in provided scope, not included in exec:exec under src/java/main? > [INFO] +- org.jboss.spec.javax.transaction:jboss-transaction-api_1.1_spec:jar:1.0.0.Final:provided > Also: NCDFE in javax_transaction/TransactionExample: > Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/logging/Logger > Probably wanna audit the whole module; is this not tested in CI? Would suggest re-implementing perhaps as unit tests instead of Main classes. > From Mike: It gets run under CI regularly (and the last build was on 22-May-2014 16:13:23). I can't remember the last time it failed. You should be able to just check out the repo and type mvn clean install from the top > From Tom: I said that we might not run exec:exec in CI as some of the QS are quite intricate and difficult to script. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2184) NoClassDefFoundError: Missing Dependency on jboss-transaction-spi

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2184?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2184. --------------------------------- Resolution: Cannot Reproduce Bug I am closing this as I can't reproduce it with the ArjunaJTA/maven quickstart: {quote} [tom@TOM-PC ~](14:37:24) $ cd projects/jbosstm/quickstart/ArjunaJTA/maven/ [tom@TOM-PC maven](master)(14:37:24) $ mvn exec:exec [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building basic maven example 5.0.4.Final-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- exec-maven-plugin:1.2:exec (default-cli) @ maven --- Sep 15, 2014 3:02:02 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager addService INFO: ARJUNA012163: Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 49387 Sep 15, 2014 3:02:02 PM com.arjuna.ats.internal.arjuna.recovery.TransactionStatusManagerItem <init> INFO: ARJUNA012337: TransactionStatusManagerItem host: 127.0.0.1 port: 49387 Sep 15, 2014 3:02:02 PM com.arjuna.ats.arjuna.recovery.TransactionStatusManager start INFO: ARJUNA012170: TransactionStatusManager started on port 49387 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService TransactionImple < ac, BasicAction: 0:ffff0a037014:c0ec:5416f15a:2 status: ActionStatus.RUNNING > null [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.602 s [INFO] Finished at: 2014-09-15T15:02:02+01:00 [INFO] Final Memory: 9M/303M [INFO] ------------------------------------------------------------------------ {quote} > NoClassDefFoundError: Missing Dependency on jboss-transaction-spi > ----------------------------------------------------------------- > > Key: JBTM-2184 > URL: https://issues.jboss.org/browse/JBTM-2184 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Affects Versions: 5.0.1 > Reporter: Andrew Rubinger > Assignee: Tom Jenkinson > > Looks like Narayana is missing a dependency, as this isn't brought in transitively: > {code}java.lang.NoClassDefFoundError: org/jboss/tm/FirstResource > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.order(XAResourceRecord.java:139) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.orderEquals(AbstractRecord.java:663) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.equals(AbstractRecord.java:227) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:379) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:144) > at com.arjuna.ats.arjuna.coordinator.BasicAction.add(BasicAction.java:307) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:647){code} > I'm also not finding the 7.x series of jboss-transaction-spi in Maven Central; is this intended? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2184) NoClassDefFoundError: Missing Dependency on jboss-transaction-spi

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2184?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2184: -------------------------------- Fix Version/s: (was: 5.0.4) > NoClassDefFoundError: Missing Dependency on jboss-transaction-spi > ----------------------------------------------------------------- > > Key: JBTM-2184 > URL: https://issues.jboss.org/browse/JBTM-2184 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTA > Affects Versions: 5.0.1 > Reporter: Andrew Rubinger > Assignee: Tom Jenkinson > > Looks like Narayana is missing a dependency, as this isn't brought in transitively: > {code}java.lang.NoClassDefFoundError: org/jboss/tm/FirstResource > at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.order(XAResourceRecord.java:139) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.orderEquals(AbstractRecord.java:663) > at com.arjuna.ats.arjuna.coordinator.AbstractRecord.equals(AbstractRecord.java:227) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:379) > at com.arjuna.ats.arjuna.coordinator.RecordList.insert(RecordList.java:144) > at com.arjuna.ats.arjuna.coordinator.BasicAction.add(BasicAction.java:307) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.enlistResource(TransactionImple.java:647){code} > I'm also not finding the 7.x series of jboss-transaction-spi in Maven Central; is this intended? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2148) Consider handling RuntimeExceptions arising from badly behaved XAResource implementations

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2148?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-2148. --------------------------------- Resolution: Won't Fix I don't think it is sustainable to add support for this but if our community thinks it beneficial we can re-open. > Consider handling RuntimeExceptions arising from badly behaved XAResource implementations > ----------------------------------------------------------------------------------------- > > Key: JBTM-2148 > URL: https://issues.jboss.org/browse/JBTM-2148 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Affects Versions: 4.17.19, 5.0.1 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > It has been observed that some XAResource implementations throw RuntimeExceptions from their XAResource::end method. > Although this is not spec compliant, it does mean that the transaction will never complete and as such afterCompletion would never be called, nor would we attempt to complete the remaining branches in the transaction. > In ArjunaCore terms the transaction would be left in the state of ActionStatus.ABORTING. > This Jira exists as a possible route for users to vote for addressing this issue. One possibility would be to try to align a RuntimeException with a response of XAResource.XA_RETRY where possible. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1954) Nothing is archived if CI job jbossts-EAP61-jdbcobjectstore fails

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1954?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-1954. ------------------------------- > Nothing is archived if CI job jbossts-EAP61-jdbcobjectstore fails > ----------------------------------------------------------------- > > Key: JBTM-1954 > URL: https://issues.jboss.org/browse/JBTM-1954 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Michael Musgrove > Assignee: Tom Jenkinson > > If an axis of CI job jbossts-EAP61-jdbcobjectstore fails no files are archived. > The job config looks perfectly fine and the files are archived if the job is successful so maybe this is a Jenkins bug to do with multi-axis jobs. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2014