May 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2163) Create an OSGi bundle activator

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2163?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2163: -------------------------------- Description: JBTM-669 has a draft implementation you can look at. (was: JBTM-669 has a draft implementation you can look at. Try to get the service running in Karaf.) > Create an OSGi bundle activator > ------------------------------- > > Key: JBTM-2163 > URL: https://issues.jboss.org/browse/JBTM-2163 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.2 > > > JBTM-669 has a draft implementation you can look at. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2163) Create an OSGi bundle activator

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2163?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2163: -------------------------------- Summary: Create an OSGi bundle activator (was: Produce an OSGi wrapper) > Create an OSGi bundle activator > ------------------------------- > > Key: JBTM-2163 > URL: https://issues.jboss.org/browse/JBTM-2163 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.2 > > > JBTM-669 has a draft implementation you can look at. Try to get the service running in Karaf. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2163) Produce an OSGi wrapper

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2163: ----------------------------------- Summary: Produce an OSGi wrapper Key: JBTM-2163 URL: https://issues.jboss.org/browse/JBTM-2163 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Jenkinson Assignee: Gytis Trikleris Fix For: 5.0.2 JBTM-669 has a draft implementation you can look at. Try to get the service running in Karaf. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2134) ArjunaCore Performance3 test failed

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2134?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-2134. ------------------------------------ Resolution: Done Last time I looked the issue was caused by to many connections to the oracle db. Doubling the number "alter system set processes=300 scope=spfile" in the oracle config should resolve the issue. > ArjunaCore Performance3 test failed > ----------------------------------- > > Key: JBTM-2134 > URL: https://issues.jboss.org/browse/JBTM-2134 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/6... > {code} > test(com.hp.mwtests.ts.arjuna.performance.Performance3) Time elapsed: 0.241 sec <<< ERROR! > java.lang.ExceptionInInitializerError: null > at com.arjuna.ats.arjuna.objectstore.StoreManager.initStore(StoreManager.java:158) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getActionStore(StoreManager.java:110) > at com.arjuna.ats.arjuna.objectstore.StoreManager.getRecoveryStore(StoreManager.java:67) > at com.arjuna.ats.arjuna.recovery.ActionStatusService.<init>(ActionStatusService.java:64) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at java.lang.Class.newInstance(Class.java:374) > at com.arjuna.ats.internal.arjuna.common.ClassloadingUtility.loadAndInstantiateClass(ClassloadingUtility.java:137) > at com.arjuna.ats.arjuna.recovery.TransactionStatusManager.start(TransactionStatusManager.java:126) > at com.arjuna.ats.arjuna.recovery.TransactionStatusManager.<init>(TransactionStatusManager.java:58) > at com.arjuna.ats.arjuna.coordinator.TxControl.createTransactionStatusManager(TxControl.java:188) > at com.arjuna.ats.arjuna.coordinator.TxControl.<clinit>(TxControl.java:264) > at com.arjuna.ats.arjuna.coordinator.BasicAction.Begin(BasicAction.java:1391) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.start(TwoPhaseCoordinator.java:76) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.start(TwoPhaseCoordinator.java:65) > at com.hp.mwtests.ts.arjuna.performance.Performance3.test(Performance3.java:49) > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2153) QA suite failure with oracle in job 71

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2153?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2153: ---------------------------------------- The oracle issue is caused by too many db connectons: bq. 2014-04-24 19:55:59,962 out: java.sql.SQLException: Listener refused the connection with the following error: bq. 2014-04-24 19:55:59,962 out: ORA-12519, TNS:no appropriate service handler found Rather than find out which test(s) are opening too many I propose to just increase the number of allowed connections. I am not sure whether the issue with DB2 is similar in nature so I will need to keep looking into those. > QA suite failure with oracle in job 71 > -------------------------------------- > > Key: JBTM-2153 > URL: https://issues.jboss.org/browse/JBTM-2153 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/7... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2153) QA suite failure with oracle in job 71

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2153?page=com.atlassian.jira.plugin.... ] Tom Jenkinson edited comment on JBTM-2153 at 5/2/14 5:41 AM: ------------------------------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/73/ was (Author: tomjenkinson): http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/ > QA suite failure with oracle in job 71 > -------------------------------------- > > Key: JBTM-2153 > URL: https://issues.jboss.org/browse/JBTM-2153 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/7... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2153) QA suite failure with oracle in job 71

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2153?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2153: -------------------------------- Priority: Major (was: Minor) > QA suite failure with oracle in job 71 > -------------------------------------- > > Key: JBTM-2153 > URL: https://issues.jboss.org/browse/JBTM-2153 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/7... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2154) QA suite failure with db2 in jobs 71 and 72

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2154?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2154: ------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/73/ > QA suite failure with db2 in jobs 71 and 72 > ------------------------------------------- > > Key: JBTM-2154 > URL: https://issues.jboss.org/browse/JBTM-2154 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/7... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2153) QA suite failure with oracle in job 71

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2153?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2153: ------------------------------------- http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/ > QA suite failure with oracle in job 71 > -------------------------------------- > > Key: JBTM-2153 > URL: https://issues.jboss.org/browse/JBTM-2153 > 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.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/7... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2162) Change CMR commit failure message

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2162?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2162: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/647, https://github.com/jbosstm/narayana/pull/648 > Change CMR commit failure message > --------------------------------- > > Key: JBTM-2162 > URL: https://issues.jboss.org/browse/JBTM-2162 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTA > Affects Versions: 4.17.19 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Trivial > Fix For: 4.17.20 > > > If a transaction containing an XA and a CMR resource is committed and the CMR resource fails the commit then the warning message mentions onePhaseCommit. Even though the CMR is in reality a one phase resource the message can be confusing. > Please change the message to something more generic. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

9 years, 12 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 2014