October 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2873) WildFly to GlassFish interop: check that recovery works

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2873?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2873: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > WildFly to GlassFish interop: check that recovery works > ------------------------------------------------------- > > Key: JBTM-2873 > URL: https://issues.jboss.org/browse/JBTM-2873 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: JTS > Affects Versions: 5.5.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Check interoperability between WildFly and GlassFish. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2912) Upgrade JMS transactional driver to JMS 2.0

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2912?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2912: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Upgrade JMS transactional driver to JMS 2.0 > ------------------------------------------- > > Key: JBTM-2912 > URL: https://issues.jboss.org/browse/JBTM-2912 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JMS > Reporter: Thomas Jenkinson > Priority: Major > Fix For: 5.next > > > The transactional driver was implemented for JMS API 1.1. We should upgrade to 2.0. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2831) Fix RTS inbound bridge participant deserialiser registration

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2831?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2831: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Fix RTS inbound bridge participant deserialiser registration > ------------------------------------------------------------ > > Key: JBTM-2831 > URL: https://issues.jboss.org/browse/JBTM-2831 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Inbound bridge participant deserialiser is registered when InboundBridgeManager is created [1]. That deserialiser is immediately used to recreate participants and update REST-AT coordinator via its HTTP resource. > In WildFly deserialiser registration used to be triggered by creating InboundBridgeManager instance in InboundBridgeService#start method. > However, Undertow subsystem update was introduced which collected and held all HTTP requests until application server completed boot-up. This caused a lock because HTTP call to REST-AT coordinator was being held and InboundBridgeService was waiting for the response. As a result server never completed boot. > Tom has removed that initialisation as a workaround [2]. Everything still works, because inbound bridge recovery manager initialises InboundBridgeManager too. However, only in the second pass. This causes warnings messages during the first cycle of the recovery by REST-AT recovery module. > I'm suggesting to remove deserialiser registration from InboundBridgeManager constructor to keep it as simple as possible and move it to other place were it could be invoked safely and on time e.g. start of first pass of InboundBridgeRecoveryModule. > [1] https://github.com/jbosstm/narayana/blob/5.5.0.Final/rts/at/bridge/src/ma... > [2] https://github.com/wildfly/wildfly/commit/6bc2e6a20b665201505f12c1c22fda9... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2855) Consider using assertions to validate locking assumptions

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2855?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2855: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Consider using assertions to validate locking assumptions > --------------------------------------------------------- > > Key: JBTM-2855 > URL: https://issues.jboss.org/browse/JBTM-2855 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 5.5.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Some methods in BasicAction assume that other methods will acquire monitors before calling them; it would aid both maintenance/readability and testing if we such methods have assert Thread.holdsLock(this); at their beginning point. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2832) Blacktie TestTPGetRely::test_tpgetrply_with_TPGETANY fail

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2832?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2832: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Blacktie TestTPGetRely::test_tpgetrply_with_TPGETANY fail > --------------------------------------------------------- > > Key: JBTM-2832 > URL: https://issues.jboss.org/browse/JBTM-2832 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Zheng Feng > Priority: Minor > Fix For: 5.next > > Attachments: CIfailure.zip > > > [exec] 1) test: TestTPGetRply::test_tpgetrply_with_TPGETANY (F) line: 272 C:\hudson\workspace\narayana-catelyn\blacktie\xatmi\src\test\cpp\TestTPGetRply.cxx > [exec] assertion failed > [exec] - Expression: _w12pq_u > [exec] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2833) Move deprecated tooling classes into an internal package

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2833?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2833: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Move deprecated tooling classes into an internal package > -------------------------------------------------------- > > Key: JBTM-2833 > URL: https://issues.jboss.org/browse/JBTM-2833 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tooling > Affects Versions: 5.5.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > commit 66a9291f56f (JBTM-2308]) "Mark classes deprecated since we need to rejig package names" marked many/most of the tooling instrumentation classes deprecated - these need to be moved to internal packages and the then marked as not deprecated. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2867) Investigate un-_workList protected access to _work object

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2867?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2867: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Investigate un-_workList protected access to _work object > --------------------------------------------------------- > > Key: JBTM-2867 > URL: https://issues.jboss.org/browse/JBTM-2867 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > Fix For: 5.next > > > During investigation of JBTM-2865 it was detected that the _work object can be accessed outside of the _workList synchronized block. Notably this seems to be a .remove() operation on it which can mutate the struct and may cause issues. > For example, this looks wrong: > https://github.com/tomjenkinson/narayana/blob/adda493b7bbd030eb405e3ef209... > If > https://github.com/tomjenkinson/narayana/blob/adda493b7bbd030eb405e3ef209... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2967) Some quickstarts are not tested in CI

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2967?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2967: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Some quickstarts are not tested in CI > ------------------------------------- > > Key: JBTM-2967 > URL: https://issues.jboss.org/browse/JBTM-2967 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Most quickstarts used to ship with a run.[sh|bat] script for running the quickstart and we used to test them in CI by executing the run script. At some point we changed the CI script (scripts/hudson/quickstart.sh) to just run the pom instead (./build.sh -B clean install). Since not all poms execute their run script we aren't getting full CI coverage. > This JIRA is to go through each quickstart and ensure the the pom does indeed exercise the quickstart. > The following poms do execute a run script > transactionaldriver-jpa-and-tomcat/pom.xml > rts/at/simple/pom.xml > rts/lra/lra-test/pom.xml > ArjunaJTS/interop/glassfish/pom.xml > transactionaldriver-and-tomcat/pom.xml > spring/camel-with-narayana-spring-boot/pom.xml > The following quickstarts contain run scripts: > transactionaldriver-jpa-and-tomcat/run.sh > ArjunaCore/txoj/run.sh > jboss-as/build/target/wildfly-9.0.0.CR1-SNAPSHOT/bin/run.sh > ArjunaJTA/object_store/run.sh > ArjunaJTA/maven/run.sh > ArjunaJTA/recovery/run.sh > ArjunaJTA/javax_transaction/run.sh > rts/at/undertow/run.sh > rts/at/recovery/recovery2/run.sh > rts/at/recovery/recovery1/run.sh > rts/at/simple/run.sh > rts/at/service/service2b/run.sh > rts/at/service/service2/run.sh > rts/at/service/service1b/run.sh > rts/at/service/service1/run.sh > rts/at/demo/run.sh > rts/lra/run.sh > ArjunaJTS/standalone/run.sh > ArjunaJTS/interop/glassfish/run.sh > ArjunaJTS/recovery/run.sh -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2998) Blacktie TestTPGetRply failed with unknown session

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2998?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2998: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Blacktie TestTPGetRply failed with unknown session > -------------------------------------------------- > > Key: JBTM-2998 > URL: https://issues.jboss.org/browse/JBTM-2998 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Zheng Feng > Priority: Minor > Fix For: 5.next > > Attachments: archive(1).zip, archive.zip > > > {noformat} > 2018-01-09 02:24:48,064 [0x00001db8] DEBUG (AtmiBrokerClient :200 ) - get session: 3 > 2018-01-09 02:24:48,064 [0x00001db8] DEBUG (AtmiBrokerClient :209 ) - did not get session: 3 > 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :411 ) - _get_tperrno > 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :415 ) - found _get_tperrno2 > 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :418 ) - returning _get_tperrno2 > 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :924 ) - tpgetrply return: -1 tperrno: 2 > 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :411 ) - _get_tperrno > 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :415 ) - found _get_tperrno2 > 2018-01-09 02:24:48,064 [0x00001db8] TRACE (XATMIc :418 ) - returning _get_tperrno2 > 2018-01-09 02:24:48,064 [0x00001db8] DEBUG (AtmiBrokerLogc :72 ) - CHKCOND ASSERT FAILED C:\hudson\workspace\narayana-catelyn\blacktie\xatmi\src\test\cpp\TestTPGetRply.cxx:272 > {noformat} > It looks like that the sessionIds have the prev id in the other tests which has not been removed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2968) Some JTS quickstarts run with JacORB

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2968?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2968: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Some JTS quickstarts run with JacORB > ------------------------------------ > > Key: JBTM-2968 > URL: https://issues.jboss.org/browse/JBTM-2968 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Some of the JTS quickstarts are using JacORB. The narayana project has since changed the default ORB (OpenJDK ORB) so we should change the quickstarts to use the new default. The affected poms are: > ArjunaJTS/pom.xml > ArjunaJTS/standalone/pom.xml > ArjunaJTS/trailmap/pom.xml -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 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 October 2019