June 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1685) QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2#Test28

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1685?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1685: ----------------------------------- Original Estimate: 2 days Remaining Estimate: 2 days > QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2#Test28 > ----------------------------------------------------------------------------------------- > > Key: JBTM-1685 > URL: https://issues.jboss.org/browse/JBTM-1685 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M4 > > Attachments: CrashRecovery02_2_Test28.zip > > Original Estimate: 2 days > Remaining Estimate: 2 days > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/99/cons... -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1686) QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1686?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1686: ----------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2 > ---------------------------------------------------------------------------------- > > Key: JBTM-1686 > URL: https://issues.jboss.org/browse/JBTM-1686 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M4 > > Attachments: crashrecovery05_2.zip, jbossts-EAP61-jdbcobjectstore_11_crashrecovery05_2.zip > > Original Estimate: 1 day > Remaining Estimate: 1 day > > http://172.17.131.2/job/jbossts-EAP61-jdbcobjectstore/DB_TYPE=postgres,jd... -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1510) QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2#CrashRecovery05_2_Test076

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1510?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1510: ----------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2#CrashRecovery05_2_Test076 > ------------------------------------------------------------------------------------------------------------ > > Key: JBTM-1510 > URL: https://issues.jboss.org/browse/JBTM-1510 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M4 > > Attachments: CrashRecovery05_2_Test076.tar.gz, TEST-org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2.txt > > Original Estimate: 1 day > Remaining Estimate: 1 day > > See: http://172.17.131.2/job/narayana/173/ -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1041) IP: A parameter is dead upon entry to a method but overwritten (IP_PARAMETER_IS_DEAD_BUT_OVERWRITTEN)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1041?page=com.atlassian.jira.plugin.... ] Tom Jenkinson edited comment on JBTM-1041 at 6/7/13 5:50 AM: ------------------------------------------------------------- Done: 3.ArjunaJTS/jts com.arjuna.ats.internal.jts.resources.ResourceRecord Line 591 The parameter toDelete to com.arjuna.ats.internal.jts.resources.ResourceRecord.remove(AbstractRecord) is dead upon entry but overwritten EDIT === To clarify, there is a commit back against this Jira for "Partial Completion" of the Jira, although there is outstanding XTS work to do. I have assigned this to Jira to Paul now. was (Author: tomjenkinson): Done: 3.ArjunaJTS/jts com.arjuna.ats.internal.jts.resources.ResourceRecord Line 591 The parameter toDelete to com.arjuna.ats.internal.jts.resources.ResourceRecord.remove(AbstractRecord) is dead upon entry but overwritten > IP: A parameter is dead upon entry to a method but overwritten (IP_PARAMETER_IS_DEAD_BUT_OVERWRITTEN) > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-1041 > URL: https://issues.jboss.org/browse/JBTM-1041 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Amos Feng > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.Final > > > 1.XTS/WSCF > com.arjuna.mwlabs.wscf.model.sagas.arjunacore.ParticipantRecord Line 540 > The parameter toDelete to com.arjuna.mwlabs.wscf.model.sagas.arjunacore.ParticipantRecord.remove(AbstractRecord) is dead upon entry but overwritten > 2.XTS/WSCF > com.arjuna.mwlabs.wscf.model.twophase.arjunacore.ParticipantRecord Line 523 > The parameter toDelete to com.arjuna.mwlabs.wscf.model.twophase.arjunacore.ParticipantRecord.remove(AbstractRecord) is dead upon entry but overwritten -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1041) IP: A parameter is dead upon entry to a method but overwritten (IP_PARAMETER_IS_DEAD_BUT_OVERWRITTEN)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1041?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1041: -------------------------------- Assignee: Paul Robinson (was: Tom Jenkinson) > IP: A parameter is dead upon entry to a method but overwritten (IP_PARAMETER_IS_DEAD_BUT_OVERWRITTEN) > ----------------------------------------------------------------------------------------------------- > > Key: JBTM-1041 > URL: https://issues.jboss.org/browse/JBTM-1041 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Amos Feng > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.Final > > > 1.XTS/WSCF > com.arjuna.mwlabs.wscf.model.sagas.arjunacore.ParticipantRecord Line 540 > The parameter toDelete to com.arjuna.mwlabs.wscf.model.sagas.arjunacore.ParticipantRecord.remove(AbstractRecord) is dead upon entry but overwritten > 2.XTS/WSCF > com.arjuna.mwlabs.wscf.model.twophase.arjunacore.ParticipantRecord Line 523 > The parameter toDelete to com.arjuna.mwlabs.wscf.model.twophase.arjunacore.ParticipantRecord.remove(AbstractRecord) is dead upon entry but overwritten -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1593) Most top level subsystem folders in the quickstart repo are missing README.md files

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1593?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1593: ----------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M4) > Most top level subsystem folders in the quickstart repo are missing README.md files > ----------------------------------------------------------------------------------- > > Key: JBTM-1593 > URL: https://issues.jboss.org/browse/JBTM-1593 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Demonstrator > Affects Versions: 5.0.0.M2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.Final > > > Top level subsystem folders in the quickstart repo are missing README.md files (except XTS). > Use the XTS README.md as an example of what they should look like. I suggest the workload assignments for completing this task as follows: > ArjunaCore - Mike > ArjunaJTA - Mike > ArjunaJTS - Mike > atsintegration - Mike > ObjectStore - Mike > blacktie Amos > rest-tx - Mike -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1641) EAP 6.1 CNFE org.jboss.tm.TxManager (from Module org.jboss.jboss-transaction-spi:main)

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1641?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1641: ----------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day > EAP 6.1 CNFE org.jboss.tm.TxManager (from Module org.jboss.jboss-transaction-spi:main) > -------------------------------------------------------------------------------------- > > Key: JBTM-1641 > URL: https://issues.jboss.org/browse/JBTM-1641 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Application Server Integration > Affects Versions: 4.17.3 > Reporter: Darryl Miles > Assignee: Michael Musgrove > Fix For: 5.0.0.M4 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > When enabling additional logging to system DEBUG on startup of standalone-full.xml it is possible to see: > 07:15:40,780 DEBUG [org.jboss.tm.TransactionManagerLocator] (MSC service thread 1-2) Unable to lookup: java:/TransactionManager: javax.naming.NameNotFoundException: Error looking up TransactionManager, service service jboss.naming.context.java.TransactionManager is not started > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:132) [jboss-as-naming-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:80) [jboss-as-naming-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:197) [jboss-as-naming-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:120) [jboss-as-naming-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:183) [jboss-as-naming-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179) [jboss-as-naming-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_17] > at org.jboss.tm.TransactionManagerLocator.tryJNDI(TransactionManagerLocator.java:150) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.tm.TransactionManagerLocator.locate(TransactionManagerLocator.java:131) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.tm.TransactionManagerLocator.locateTransactionManager(TransactionManagerLocator.java:94) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<init>(ServerVMClientUserTransaction.java:93) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<clinit>(ServerVMClientUserTransaction.java:60) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:115) [jboss-as-transactions-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > 07:15:40,786 DEBUG [org.jboss.tm.TransactionManagerLocator] (MSC service thread 1-2) Unable to instantiate legacy transaction manager: java.lang.ClassNotFoundException: org.jboss.tm.TxManager from [Module "org.jboss.jboss-transaction-spi:main" from local module loader @634f6b14 (finder: local module finder @72ff20fb (roots: F:\Devel\deps\jboss-eap-6.1\modules,F:\Devel\deps\jboss-eap-6.1\modules\system\layers\base))] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.2.0.CR1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.2.0.CR1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.2.0.CR1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.2.0.CR1] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.2.0.CR1] > at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_17] > at java.lang.Class.forName(Class.java:188) [rt.jar:1.7.0_17] > at org.jboss.tm.TransactionManagerLocator.usePrivateAPI(TransactionManagerLocator.java:172) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.tm.TransactionManagerLocator.locate(TransactionManagerLocator.java:133) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.tm.TransactionManagerLocator.locateTransactionManager(TransactionManagerLocator.java:94) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<init>(ServerVMClientUserTransaction.java:93) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<clinit>(ServerVMClientUserTransaction.java:60) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final] > at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:115) [jboss-as-transactions-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1708) readme instructions for starting the standalone transaction manager are incorrect

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1708?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1708: ----------------------------------- Original Estimate: 1 day Remaining Estimate: 1 day Fix Version/s: 5.0.0.M4 > readme instructions for starting the standalone transaction manager are incorrect > --------------------------------------------------------------------------------- > > Key: JBTM-1708 > URL: https://issues.jboss.org/browse/JBTM-1708 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 4.17.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.0.M4 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > The instructions in ./narayana-full/readme.txt for starting the transaction manager don't work. Also the script for starting the TM only starts the JTS version. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1464) Some performance tests are missing the timing code.

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1464?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1464: ----------------------------------- Fix Version/s: 5.0.0.Final > Some performance tests are missing the timing code. > --------------------------------------------------- > > Key: JBTM-1464 > URL: https://issues.jboss.org/browse/JBTM-1464 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing, Transaction Core > Affects Versions: 4.17.3 > Reporter: Mark Little > Assignee: Michael Musgrove > Priority: Trivial > Fix For: 5.0.0.Final > > > The TXOJ performance tests are supposed to get the start time before running and then the end time after completion, printing out the difference. It seems that in several of them, the end time is no longer obtained and nothing is printed out either, i.e., no elapsed time is given. This makes these tests pretty useless as performance tests. Rather than remove the tests, the elapsed time check should be put back. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by AS7

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1339: ----------------------------------- Assignee: Gytis Trikleris (was: Michael Musgrove) > Ensure that JTS can use the JDK ORB provided by AS7 > --------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.0.0.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > -- 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, 4 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 June 2013