June 2013 - jbossts-issues - Jboss List Archives

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

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1686?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-1686: --------------------------------------- http://172.17.131.2/job/jbossts-EAP61-jdbcobjectstore/DB_TYPE=db2,jdk=jdk... Use jbossts-EAP61-jdbcobjectstore_11_crashrecovery05_2.zip > 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 > > > 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, 7 months

1
0
0 / 0

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

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1686?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1686: ---------------------------------- Attachment: jbossts-EAP61-jdbcobjectstore_11_crashrecovery05_2.zip > 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 > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1709) NPE during deploy the restat-web.war

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1709?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1709: ---------------------------- Priority: Minor (was: Major) > NPE during deploy the restat-web.war > ------------------------------------ > > Key: JBTM-1709 > URL: https://issues.jboss.org/browse/JBTM-1709 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Application Server Integration, BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.M4 > > > http://172.17.131.2/job/blacktie-linux64-el5/1545/ > {noformat} > 13:38:34,246 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.undertow.deployment.default-host./rest-tx: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-host./rest-tx: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > 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] > Caused by: java.lang.RuntimeException: java.lang.NullPointerException > at io.undertow.servlet.core.CompositeThreadSetupAction$1.tearDown(CompositeThreadSetupAction.java:59) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:196) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:75) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > ... 3 more > Caused by: java.lang.NullPointerException > at org.jboss.jca.core.connectionmanager.ccm.CachedConnectionManagerImpl.popMetaAwareObject(CachedConnectionManagerImpl.java:240) > at org.jboss.as.connector.deployers.ra.processors.CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.teardown(CachedConnectionManagerSetupProcessor.java:107) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$1$1.tearDown(UndertowDeploymentInfoService.java:214) > at io.undertow.servlet.core.CompositeThreadSetupAction$1.tearDown(CompositeThreadSetupAction.java:52) > ... 7 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1733) HelpTest in btadmin failed with "Command was unsuccessful"

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1733?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1733: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > HelpTest in btadmin failed with "Command was unsuccessful" > ---------------------------------------------------------- > > Key: JBTM-1733 > URL: https://issues.jboss.org/browse/JBTM-1733 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.0.M4 > > > http://172.17.131.2/job/blacktie-linux/3/jdk=jdk7.latest,label_exp=linux3... > It looks like caused by the "&&" characters in the directory path. -- 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, 7 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: ----------------------------------- Component/s: Application Server Integration > 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 > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1739) Remove owner field from TwoPhaseVolatileStore

by Mark Little (JIRA)

Mark Little created JBTM-1739: --------------------------------- Summary: Remove owner field from TwoPhaseVolatileStore Key: JBTM-1739 URL: https://issues.jboss.org/browse/JBTM-1739 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 5.0.0.M3 Reporter: Mark Little Assignee: Tom Jenkinson Fix For: 5.0.0.M4 We associated states in TPVS with the creating (or using) thread. This really doesn't make sense, since locking can be done elsewhere if necessary and it's not a property that is required by the object store implementation or supported by other implementations. I can't recall why I did this in the first place, but possibly had another scenario in mind. But at the moment it's a restriction that does not make sense. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1739) Remove owner field from TwoPhaseVolatileStore

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1739?page=com.atlassian.jira.plugin.... ] Mark Little closed JBTM-1739. ----------------------------- > Remove owner field from TwoPhaseVolatileStore > --------------------------------------------- > > Key: JBTM-1739 > URL: https://issues.jboss.org/browse/JBTM-1739 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > Fix For: 5.0.0.M4 > > > We associated states in TPVS with the creating (or using) thread. This really doesn't make sense, since locking can be done elsewhere if necessary and it's not a property that is required by the object store implementation or supported by other implementations. > I can't recall why I did this in the first place, but possibly had another scenario in mind. But at the moment it's a restriction that does not make sense. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1739) Remove owner field from TwoPhaseVolatileStore

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1739?page=com.atlassian.jira.plugin.... ] Mark Little updated JBTM-1739: ------------------------------ Assignee: Mark Little (was: Tom Jenkinson) > Remove owner field from TwoPhaseVolatileStore > --------------------------------------------- > > Key: JBTM-1739 > URL: https://issues.jboss.org/browse/JBTM-1739 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > Fix For: 5.0.0.M4 > > > We associated states in TPVS with the creating (or using) thread. This really doesn't make sense, since locking can be done elsewhere if necessary and it's not a property that is required by the object store implementation or supported by other implementations. > I can't recall why I did this in the first place, but possibly had another scenario in mind. But at the moment it's a restriction that does not make sense. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1739) Remove owner field from TwoPhaseVolatileStore

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1739?page=com.atlassian.jira.plugin.... ] Mark Little resolved JBTM-1739. ------------------------------- Resolution: Done > Remove owner field from TwoPhaseVolatileStore > --------------------------------------------- > > Key: JBTM-1739 > URL: https://issues.jboss.org/browse/JBTM-1739 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Tom Jenkinson > Fix For: 5.0.0.M4 > > > We associated states in TPVS with the creating (or using) thread. This really doesn't make sense, since locking can be done elsewhere if necessary and it's not a property that is required by the object store implementation or supported by other implementations. > I can't recall why I did this in the first place, but possibly had another scenario in mind. But at the moment it's a restriction that does not make sense. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1738) Allow sharing of states between address spaces for STM applications and add some tests.

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1738?page=com.atlassian.jira.plugin.... ] Mark Little closed JBTM-1738. ----------------------------- > Allow sharing of states between address spaces for STM applications and add some tests. > --------------------------------------------------------------------------------------- > > Key: JBTM-1738 > URL: https://issues.jboss.org/browse/JBTM-1738 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: STM > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > Fix For: 5.0.0.M4 > > > Support ObjectModel.MULTIPLE in the containers. -- 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, 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 June 2013