May 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1691) Auto-merge in narayana.sh is not robust enough

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1691: ----------------------------------- Summary: Auto-merge in narayana.sh is not robust enough Key: JBTM-1691 URL: https://issues.jboss.org/browse/JBTM-1691 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Reporter: Paul Robinson Assignee: Tom Jenkinson Fix For: 4.17.5, 5.0.0.M3 This can't be auto=merged: {code} <<<<<<< HEAD <version.org.jboss.jbossts.jbossjts>5.0.0.M2</version.org.jboss.jbossts.jbossjts> <version.org.jboss.jbossts.jbossjts-integration>5.0.0.M2</version.org.jboss.jbossts.jbossjts-integration> <version.org.jboss.jbossts.jbossxts>5.0.0.M2</version.org.jboss.jbossts.jbossxts> <version.org.jboss.jboss-vfs>3.2.0.Beta1</version.org.jboss.jboss-vfs> <version.org.jboss.jbossts.narayana>5.0.0.M2</version.org.jboss.jbossts.narayana> ======= <version.org.jboss.jbossts.jbossjts>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossjts> <version.org.jboss.jbossts.jbossjts-integration>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossjts-integration> <version.org.jboss.jbossts.jbossxts>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.jbossxts> <version.org.jboss.jboss-vfs>3.1.0.Final</version.org.jboss.jboss-vfs> <version.org.jboss.jbossts.narayana>5.0.0.M3-SNAPSHOT</version.org.jboss.jbossts.narayana> >>>>>>> Upgrade Narayana to 5.0.0.M3-SNAPSHOT {code} Our current strategy will take our version which results in the old version of jboss-vfs being used, which in turn causes a build failure in WildFly. Maybe we should remove the auto-merge and replace with a manual intervention when a conflict occurs? -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1690) Upload orson and emma to repository.jboss.org

by Weinan Li (JIRA)

Weinan Li created JBTM-1690: ------------------------------- Summary: Upload orson and emma to repository.jboss.org Key: JBTM-1690 URL: https://issues.jboss.org/browse/JBTM-1690 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System Affects Versions: 4.17.4 Reporter: Weinan Li Assignee: Tom Jenkinson Priority: Minor Could orson and emma be uploaded to repository.jboss.org, so that the paths wouldn't need to be set on the command line? -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1689) "jta" vs. "jts" profile seems duplicate

by Weinan Li (JIRA)

[ https://issues.jboss.org/browse/JBTM-1689?page=com.atlassian.jira.plugin.... ] Weinan Li updated JBTM-1689: ---------------------------- Priority: Minor (was: Major) Description: "jta" vs. "jts" profile, they seem to build the same modules except for ArjunaJTS. As maven has some built in options for selecting which modules/directories to build, would it be better to just use those options? Instead of defining profiles, it might look something like "mvn install -pl common,ArjunaCore" instead of the build profile "mvn install -Pcore" was: Currently we have tanuki in these components: {code} ArjunaCore/arjuna/services/pom.xml ArjunaJTS/narayana-jts-idlj/pom.xml ArjunaJTS/narayana-jts-jacorb/pom.xml pom.xml {code} {code} <dependency> <groupId>tanukisoft</groupId> <artifactId>wrapper</artifactId> <version>${version.tanukisoft}</version> </dependency> {code} We need to remove these dependencies from eap6 profile according to comments from Fernando: {quote} We do not ship tanukiwrapper with the AS (the windows on is an exceptional case and for different reasons). It is not in the AS7 dependencies, and it will be hard for Support to properly rebuild TS in the field. {quote} btw, there are two classes we need to remove from eap6 profile which depends on tanuki wrapper: {code} ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/services/recovery/RecoveryManagerService.java ArjunaJTS/jts/services/classes/com/arjuna/ats/jts/services/transactionserver/TransactionServerService.java {code} > "jta" vs. "jts" profile seems duplicate > --------------------------------------- > > Key: JBTM-1689 > URL: https://issues.jboss.org/browse/JBTM-1689 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.4 > Reporter: Weinan Li > Assignee: Tom Jenkinson > Priority: Minor > > "jta" vs. "jts" profile, they seem to build the same modules except for ArjunaJTS. > As maven has some built in options for selecting which modules/directories to build, would it be better to just use those options? Instead of defining profiles, it might look something like "mvn install -pl common,ArjunaCore" instead of the build profile "mvn install -Pcore" -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1689) "jta" vs. "jts" profile seems duplicate

by Weinan Li (JIRA)

Weinan Li created JBTM-1689: ------------------------------- Summary: "jta" vs. "jts" profile seems duplicate Key: JBTM-1689 URL: https://issues.jboss.org/browse/JBTM-1689 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System Affects Versions: 4.17.4 Reporter: Weinan Li Assignee: Tom Jenkinson Currently we have tanuki in these components: {code} ArjunaCore/arjuna/services/pom.xml ArjunaJTS/narayana-jts-idlj/pom.xml ArjunaJTS/narayana-jts-jacorb/pom.xml pom.xml {code} {code} <dependency> <groupId>tanukisoft</groupId> <artifactId>wrapper</artifactId> <version>${version.tanukisoft}</version> </dependency> {code} We need to remove these dependencies from eap6 profile according to comments from Fernando: {quote} We do not ship tanukiwrapper with the AS (the windows on is an exceptional case and for different reasons). It is not in the AS7 dependencies, and it will be hard for Support to properly rebuild TS in the field. {quote} btw, there are two classes we need to remove from eap6 profile which depends on tanuki wrapper: {code} ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/services/recovery/RecoveryManagerService.java ArjunaJTS/jts/services/classes/com/arjuna/ats/jts/services/transactionserver/TransactionServerService.java {code} -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-849) registerSynchronization fails with wrong status message

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/JBTM-849?page=com.atlassian.jira.plugin.s... ] Johnathon Lee edited comment on JBTM-849 at 5/15/13 9:35 AM: ------------------------------------------------------------- >From a support perspective, the more understandable the message is the better for the user/support. ie: the clarity of the newer message may actually prevent cases. The KCS system would be used to correlate the old message with the new message. > registerSynchronization fails with wrong status message > ------------------------------------------------------- > > Key: JBTM-849 > URL: https://issues.jboss.org/browse/JBTM-849 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.15.1 > Environment: https://github.com/jbossejb3/jboss-as/tree/991e836c1bcb6b471010c5930fc3f5... > Reporter: Carlo de Wolf > Assignee: Tom Jenkinson > Attachments: JBTM-849-stracktrace.txt > > > registerSynchronization is called from within a beforeCompletion of another Synchronization. I would expect the status to be PREPARING (or anything but RUNNING). > {noformat} > java.lang.IllegalStateException: Synchronizations are not allowed! Transaction status isActionStatus.RUNNING > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronizationImple(TransactionImple.java:367) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.registerSynchronization(TransactionImple.java:344) > at org.jboss.jca.core.connectionmanager.transaction.TransactionSynchronizer.getRegisteredSynchronizer(TransactionSynchronizer.java:198) > at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.enlist(TxConnectionListener.java:210) > at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.managedConnectionReconnected(TxConnectionManagerImpl.java:407) > ... 104 more > {noformat} -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1688) TXBridge doesn't support "loops" or "diamonds"

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1688: ----------------------------------- Summary: TXBridge doesn't support "loops" or "diamonds" Key: JBTM-1688 URL: https://issues.jboss.org/browse/JBTM-1688 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: TxBridge, XTS Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.Final See here: http://docs.jboss.org/jbosstm/5.0.0.M2/guides/txbridge_guide/index.html#d... -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1658) Test Hang: com.hp.mwtests.ts.txoj.threadaction.ThreadActionTest

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1658?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-1658. ------------------------------------ Resolution: Won't Fix This looks like a one off and I don't have access to the logs for the failed test case so closing as won't fix > Test Hang: com.hp.mwtests.ts.txoj.threadaction.ThreadActionTest > --------------------------------------------------------------- > > Key: JBTM-1658 > URL: https://issues.jboss.org/browse/JBTM-1658 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Testing, Transaction Core > Reporter: Paul Robinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M3 > > > See here: > http://172.17.131.2/job/narayana/TESTS=MAIN,jdk=jdk7.latest,label=linux/2... -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1661) Implement JTA 1.2 @TransactionScoped feature

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1661?focusedWorklogId=12429196&page=... ] Paul Robinson logged work on JBTM-1661: --------------------------------------- Author: Paul Robinson Created on: 13/May/13 2:51 PM Start Date: 13/May/13 2:51 PM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 1 day (was: 1 day, 2 hours) Time Spent: 1 day (was: 6 hours) Worklog Id: (was: 12429196) > Implement JTA 1.2 @TransactionScoped feature > -------------------------------------------- > > Key: JBTM-1661 > URL: https://issues.jboss.org/browse/JBTM-1661 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JTA > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Critical > Fix For: 5.0.0.M3 > > Original Estimate: 2 days > Time Spent: 1 day > Remaining Estimate: 1 day > > Implement Section "3.8 TransactionScoped Annotation" of the JTA 1.2 specification. -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1660) Implement JTA 1.2 @Transactional feature

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1660?focusedWorklogId=12429195&page=... ] Paul Robinson logged work on JBTM-1660: --------------------------------------- Author: Paul Robinson Created on: 13/May/13 2:51 PM Start Date: 13/May/13 2:51 PM Worklog Time Spent: 2 hours Issue Time Tracking ------------------- Remaining Estimate: 2 days, 3 hours (was: 2 days, 5 hours) Time Spent: 1 day, 5 hours (was: 1 day, 3 hours) Worklog Id: (was: 12429195) > Implement JTA 1.2 @Transactional feature > ---------------------------------------- > > Key: JBTM-1660 > URL: https://issues.jboss.org/browse/JBTM-1660 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JTA > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Critical > Fix For: 5.0.0.M3 > > Original Estimate: 4 days > Time Spent: 1 day, 5 hours > Remaining Estimate: 2 days, 3 hours > > Implement Section "3.7 Transactional Annotation" of the JTA 1.2 specification. -- 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

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1611) Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09, 10, 12 with jacorb and HornetQ object store enabled

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-1611?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka commented on JBTM-1611: ---------------------------------------- I think that it's because the -Dprofile-hornetq was added in 4.17.4.Final. When you use that flag on previous version the hornetq object store is not activated in the fact. I've patched the 4.17.3.Final and the test is failing as well. > Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09,10,12 with jacorb and HornetQ object store enabled > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1611 > URL: https://issues.jboss.org/browse/JBTM-1611 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 4.17.3 > Reporter: Ondřej Chaloupka > Assignee: Michael Musgrove > Fix For: 4.17.5, 5.0.0.M3 > > Attachments: 0001-JBTM-1611-Make-recovery-passes-configurable.patch > > > During testing EAP 6.1.0.ER3 I'm hitting problem on QA tests of narayana project for branch 4.17 when running qa tests with jacorb and hornetq object store (happening for NIO and AIO). > Tests which are failing: > org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09 > - CrashRecovery09_Test01 > - CrashRecovery09_Test03 > - CrashRecovery09_Test05 > org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery10 > - CrashRecovery10_Test01 > - CrashRecovery10_Test03 > - CrashRecovery10_Test05 > org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery12 > - CrashRecovery12_Test03 > - CrashRecovery12_Test06 > Detailed log could be found in job: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-61-jbossts-qa-te... > I was trying to get more info on the test CrashRecovery09 but I can say just that the value honlder has value 0 instead of 1 on org.jboss.jbossts.qa.CrashRecovery09Clients.Client01a (line 84). -- 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

11 years, 6 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 May 2013