March 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2352) JDBC test suite fails if an XA DataSource does not implement javax.sql.DataSource

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2352?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2352: ----------------------------------- Description: I tried testing a new JDBC driver with the qa test suite. The test fail unless the XA DataSource implements javax.sql.DataSource: {code} ccessors.DynamicDataSourceJDBCAccess@61d38439 : java.lang.ClassCastException: com.impossibl.postgres.jdbc.xa.PGXADataSource cannot be cast to javax.sql.DataSource 2015-03-12 14:21:08,176 out: at com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess.initialise(DynamicDataSourceJDBCAccess.java:84) 2015-03-12 14:21:08,176 err: 2015-03-12 14:21:08.176 FINE POA RootPOA... done 2015-03-12 14:21:08,176 out: at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.<init>(JDBCStore.java:214) {code} In addition the jdbc testsuite only works with XADataSources that implement javax.naming.Referenceable. As part of the fix we should investigate whether using com/arjuna/ats/internal/jdbc/ProvidedXADataSourceConnection will remove this restriction. was: I tried testing a new JDBC driver with the qa test suite. The test fail unless the XA DataSource implements javax.sql.transaction: {code} ccessors.DynamicDataSourceJDBCAccess@61d38439 : java.lang.ClassCastException: com.impossibl.postgres.jdbc.xa.PGXADataSource cannot be cast to javax.sql.DataSource 2015-03-12 14:21:08,176 out: at com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess.initialise(DynamicDataSourceJDBCAccess.java:84) 2015-03-12 14:21:08,176 err: 2015-03-12 14:21:08.176 FINE POA RootPOA... done 2015-03-12 14:21:08,176 out: at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.<init>(JDBCStore.java:214) {code} In addition the jdbc testsuite only works with XADataSources that implement javax.naming.Referenceable. As part of the fix we should investigate whether using com/arjuna/ats/internal/jdbc/ProvidedXADataSourceConnection will remove this restriction. > JDBC test suite fails if an XA DataSource does not implement javax.sql.DataSource > --------------------------------------------------------------------------------- > > Key: JBTM-2352 > URL: https://issues.jboss.org/browse/JBTM-2352 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > I tried testing a new JDBC driver with the qa test suite. The test fail unless the XA DataSource implements javax.sql.DataSource: > {code} > ccessors.DynamicDataSourceJDBCAccess@61d38439 : java.lang.ClassCastException: com.impossibl.postgres.jdbc.xa.PGXADataSource cannot be cast to javax.sql.DataSource > 2015-03-12 14:21:08,176 out: at com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess.initialise(DynamicDataSourceJDBCAccess.java:84) > 2015-03-12 14:21:08,176 err: 2015-03-12 14:21:08.176 FINE POA RootPOA... done > 2015-03-12 14:21:08,176 out: at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.<init>(JDBCStore.java:214) > {code} > In addition the jdbc testsuite only works with XADataSources that implement javax.naming.Referenceable. As part of the fix we should investigate whether using com/arjuna/ats/internal/jdbc/ProvidedXADataSourceConnection will remove this restriction. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2352) JDBC test suite fails if a DataSource does not implement javax.sql.DataSource

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2352: -------------------------------------- Summary: JDBC test suite fails if a DataSource does not implement javax.sql.DataSource Key: JBTM-2352 URL: https://issues.jboss.org/browse/JBTM-2352 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Affects Versions: 5.0.4 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.0.5 I tried testing a new JDBC driver with the qa test suite. The test fail unless the XA DataSource implements javax.sql.transaction: {code} ccessors.DynamicDataSourceJDBCAccess@61d38439 : java.lang.ClassCastException: com.impossibl.postgres.jdbc.xa.PGXADataSource cannot be cast to javax.sql.DataSource 2015-03-12 14:21:08,176 out: at com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DynamicDataSourceJDBCAccess.initialise(DynamicDataSourceJDBCAccess.java:84) 2015-03-12 14:21:08,176 err: 2015-03-12 14:21:08.176 FINE POA RootPOA... done 2015-03-12 14:21:08,176 out: at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.<init>(JDBCStore.java:214) {code} In addition the jdbc testsuite only works with XADataSources that implement javax.naming.Referenceable. As part of the fix we should investigate whether using com/arjuna/ats/internal/jdbc/ProvidedXADataSourceConnection will remove this restriction. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2351) XTS qa tests fail to stop WildFly after excecution

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2351?page=com.atlassian.jira.plugin.... ] Gytis Trikleris edited comment on JBTM-2351 at 3/12/15 11:47 AM: ----------------------------------------------------------------- Log entries indicating the cause of the problem: WS-AT: WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046032: no XTS application recovery module found to help reactivate recovered WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 WS-BA: WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046044: no XTS application recovery module found to help reactivate recovered WS-BA participant org.jboss.jbossts.xts.servicetests.CoordinatorCompletionParticipant.0 And common deployment error: {code} ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."xtstest.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xtstest.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "xtstest.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.NullPointerException at org.jboss.ws.common.configuration.AbstractCommonConfigResolver.resolveEndpointConfig(AbstractCommonConfigResolver.java:129) at org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_HANDLER.processAnnotation(WSIntegrationProcessorJAXWS_HANDLER.java:95) at org.jboss.as.webservices.deployers.AbstractIntegrationProcessorJAXWS.deploy(AbstractIntegrationProcessorJAXWS.java:74) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) ... 5 more {code} was (Author: gytis): Log entries indicating the cause of the problem: WS-AT: WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046032: no XTS application recovery module found to help reactivate recovered WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 WS-BA: WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046044: no XTS application recovery module found to help reactivate recovered WS-BA participant org.jboss.jbossts.xts.servicetests.CoordinatorCompletionParticipant.0 > XTS qa tests fail to stop WildFly after excecution > -------------------------------------------------- > > Key: JBTM-2351 > URL: https://issues.jboss.org/browse/JBTM-2351 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/179/console -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2351) XTS qa tests fail to stop WildFly after excecution

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2351?page=com.atlassian.jira.plugin.... ] Gytis Trikleris edited comment on JBTM-2351 at 3/12/15 10:33 AM: ----------------------------------------------------------------- Log entries indicating the cause of the problem: WS-AT: WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046032: no XTS application recovery module found to help reactivate recovered WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 WS-BA: WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046044: no XTS application recovery module found to help reactivate recovered WS-BA participant org.jboss.jbossts.xts.servicetests.CoordinatorCompletionParticipant.0 was (Author: gytis): Log entries indicating the cause of the problem: WS-AT: {code} WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046032: no XTS application recovery module found to help reactivate recovered WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 {code} WS-BA: {code} WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046044: no XTS application recovery module found to help reactivate recovered WS-BA participant org.jboss.jbossts.xts.servicetests.CoordinatorCompletionParticipant.0 {code} > XTS qa tests fail to stop WildFly after excecution > -------------------------------------------------- > > Key: JBTM-2351 > URL: https://issues.jboss.org/browse/JBTM-2351 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/179/console -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2351) XTS qa tests fail to stop WildFly after excecution

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2351?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2351: --------------------------------------- Log entries indicating the cause of the problem: WS-AT: {code} WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046032: no XTS application recovery module found to help reactivate recovered WS-AT participant org.jboss.jbossts.xts.servicetests.DurableTestParticipant.0 {code} WS-BA: {code} WARN [com.arjuna.wsrecovery] (Periodic Recovery) ARJUNA046044: no XTS application recovery module found to help reactivate recovered WS-BA participant org.jboss.jbossts.xts.servicetests.CoordinatorCompletionParticipant.0 {code} > XTS qa tests fail to stop WildFly after excecution > -------------------------------------------------- > > Key: JBTM-2351 > URL: https://issues.jboss.org/browse/JBTM-2351 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.5 > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/179/console -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2245) Narayana TM should act upon wildfly suspend calls

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2245?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2245: -------------------------------- Component/s: XTS > Narayana TM should act upon wildfly suspend calls > ------------------------------------------------- > > Key: JBTM-2245 > URL: https://issues.jboss.org/browse/JBTM-2245 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration, XTS > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > Wildfly now supports suspend [notifications | http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002862.html] > The design discussion is [here| http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002296.html] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2245) Narayana TM should act upon wildfly suspend calls

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2245?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2245: -------------------------------- Forum Reference: https://developer.jboss.org/thread/252905 > Narayana TM should act upon wildfly suspend calls > ------------------------------------------------- > > Key: JBTM-2245 > URL: https://issues.jboss.org/browse/JBTM-2245 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > Wildfly now supports suspend [notifications | http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002862.html] > The design discussion is [here| http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002296.html] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2245) Narayana TM should act upon wildfly suspend calls

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2245?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2245: ----------------------------------- Assignee: Michael Musgrove (was: Tom Jenkinson) > Narayana TM should act upon wildfly suspend calls > ------------------------------------------------- > > Key: JBTM-2245 > URL: https://issues.jboss.org/browse/JBTM-2245 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > Wildfly now supports suspend [notifications | http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002862.html] > The design discussion is [here| http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002296.html] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2245) Narayana TM should act upon wildfly suspend calls

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2245?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2245: -------------------------------- Fix Version/s: 5.0.5 (was: 5.x.y) > Narayana TM should act upon wildfly suspend calls > ------------------------------------------------- > > Key: JBTM-2245 > URL: https://issues.jboss.org/browse/JBTM-2245 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.5 > > > Wildfly now supports suspend [notifications | http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002862.html] > The design discussion is [here| http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002296.html] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-2349) CompensationContext is destroyed once the first handler is invoked

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2349?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2349: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/813 > CompensationContext is destroyed once the first handler is invoked > ------------------------------------------------------------------ > > Key: JBTM-2349 > URL: https://issues.jboss.org/browse/JBTM-2349 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.0.5 > > > https://github.com/jbosstm/narayana/blob/master/compensations/src/main/ja... > https://github.com/jbosstm/narayana/blob/master/compensations/src/main/ja... > If there are two handlers (compensation or confirmation), which need to access the same compensation scoped object, only the first one will succeed. Once the first handler is invoked from the ParticipantImpl, CompensationScope is destroyed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2015