February 2018 - jbossts-issues - Jboss List Archives

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

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2867?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2867: ---------------------------------- Fix Version/s: 5.next (was: 5.8.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: Tom Jenkinson > Assignee: Tom Jenkinson > 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.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2965) Unused source directory in the quickstart repository

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2965?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2965: ---------------------------------- Fix Version/s: 5.next (was: 5.8.0.Final) > Unused source directory in the quickstart repository > ---------------------------------------------------- > > Key: JBTM-2965 > URL: https://issues.jboss.org/browse/JBTM-2965 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > There is an artifact in our quickstart repo that does not look like a quickstart and no other pom in the quickstart and performance repositories references the artifact: > https://github.com/jbosstm/quickstart/tree/master/ArjunaJTS/jta > It has never changed since the initial commit: > {quote} > commit caabc37803bac12e47f4986baca21f9052e14abc > Author: Tom Jenkinson <tom.jenkinson(a)redhat.com> > Date: Tue Oct 2 11:05:51 2012 +0100 > Initial version of a performance comparitor for jts and jta > {quote} > This artefact needs deleting. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

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

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2968?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2968: ---------------------------------- Fix Version/s: 5.next (was: 5.8.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 > 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.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2989) Replace to use the DBCP2 in the spring quickstarts

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2989?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2989: ---------------------------------- Fix Version/s: 5.next (was: 5.8.0.Final) > Replace to use the DBCP2 in the spring quickstarts > -------------------------------------------------- > > Key: JBTM-2989 > URL: https://issues.jboss.org/browse/JBTM-2989 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > It could be helpful to replace the transational driver when using with the spring. The transactional driver might be only used in the standalone. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2995) RTS InboundBridgeRecoveryTestCase hanging

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2995?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2995: ---------------------------------- Fix Version/s: 5.next (was: 5.8.0.Final) > RTS InboundBridgeRecoveryTestCase hanging > ----------------------------------------- > > Key: JBTM-2995 > URL: https://issues.jboss.org/browse/JBTM-2995 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.7.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The following test is hanging: > org.jboss.narayana.rest.bridge.inbound.test.integration.InboundBridgeRecoveryTestCase > and the WildFly server log for the run is reporting that TM recovery is starting before the ORB has initialised and therefore the deploy of the test fails: > 2018-02-20 01:56:03,233 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) ARJUNA012087: Activate of atomic action with id 0:ffffac110014:-3aed03e2:5a8b802e:14 and type /StateManager/BasicAction/TwoPhaseCoordinat > or/ArjunaTransactionImple/ServerTransaction/JCA unexpectedly failed, could not load state. > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (MSC service thread 1-7) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 FATAL [com.arjuna.ats.jts] (Periodic Recovery) ARJUNA022006: The ORB has not been initialized yet > 2018-02-20 01:56:03,236 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" com.arjuna.ats.arjuna.exceptions.FatalError > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > 2018-02-20 01:56:03,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.txn.context.local: org.jboss.msc.service.StartException in service jboss.txn.context.l > ocal: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1527) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) > at com.arjuna.ats.internal.jts.orbspecific.ControlImple.createTransactionHandle(ControlImple.java:524) > at com.arjuna.ats.internal.jts.orbspecific.interposition.ServerControl.<init>(ServerControl.java:223) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.SubordinateAtomicTransaction.<init>(SubordinateAtomicTransaction.java:71) > at com.arjuna.ats.internal.jta.transaction.jts.subordinate.jca.TransactionImple.<init>(TransactionImple.java:77) > at com.arjuna.ats.internal.jta.transaction.jts.jca.TransactionImporterImple.recoverTransaction(TransactionImporterImple.java:98) > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.doRecover(XATerminatorImple.java:434) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider.<init>(JBossLocalTransactionProvider.java:85) > at org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider.<init>(JBossJTALocalTransactionProvider.java:52) > at org.wildfly.transaction.client.provider.jboss.JBossLocalTransactionProvider$Builder.build(JBossLocalTransactionProvider.java:746) > at org.jboss.as.txn.service.LocalTransactionContextService.start(LocalTransactionContextService.java:57) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1701) > 2018-02-20 01:56:03,237 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.jts.ORBManager > .getPOA(ORBManager.java:97) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979) > at java.lang.Thread.run(Thread.java:748) > Caused by: com.arjuna.ats.arjuna.exceptions.FatalError > at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:97) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

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

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2967?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2967: ---------------------------------- Fix Version/s: 5.next (was: 5.8.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 > 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.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2913) Make the SPI a true dependency of standalone narayana-jta pom.xml

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2913?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2913: ---------------------------------- Fix Version/s: 5.next (was: 5.8.0.Final) > Make the SPI a true dependency of standalone narayana-jta pom.xml > ----------------------------------------------------------------- > > Key: JBTM-2913 > URL: https://issues.jboss.org/browse/JBTM-2913 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > This means that users can simply import the narayana-jta dependency rather than both it and the SPI. > It is useful when being consumed by jbpm for example. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2966) narayana-quickstarts-jts quickstart does not run standalone

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2966?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2966: ---------------------------------- Fix Version/s: 5.next (was: 5.8.0.Final) > narayana-quickstarts-jts quickstart does not run standalone > ----------------------------------------------------------- > > Key: JBTM-2966 > URL: https://issues.jboss.org/browse/JBTM-2966 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.7.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The recovery quickstart does not run due to missing maven jboss-transaction-spi dependency. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2996) Change the Narayana CI jobs to consider membership of PR author

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2996?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka resolved JBTM-2996. ----------------------------------- Resolution: Done > Change the Narayana CI jobs to consider membership of PR author > --------------------------------------------------------------- > > Key: JBTM-2996 > URL: https://issues.jboss.org/browse/JBTM-2996 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System > Affects Versions: 5.7.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > It would be good to start using gihub webhooks instead of a poller jenkins cron job. > Configure the triggers in Jenkins and webhook on github and consider using the plugin > https://wiki.jenkins.io/display/JENKINS/GitHub+pull+request+builder+plugin -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2996) Change the Narayana CI jobs to consider membership of PR author

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2996?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka edited comment on JBTM-2996 at 2/23/18 6:37 AM: ---------------------------------------------------------------- I distributed the change to all _pulls_ `-poller` jobs was (Author: ochaloup): I distributed the change to all _pulls_ `-poller` jobs. I ended up with the following ```bash export GIT_ACCOUNT=jbosstm export GIT_REPO=narayana export COMMENT_ON_PULL=1 function comment_on_pull { if [ "$COMMENT_ON_PULL" = "" ]; then return; fi PULL_NUMBER=$(echo $GIT_BRANCH | awk -F 'pull' '{ print $2 }' | awk -F '/' '{ print $2 }') if [ "$PULL_NUMBER" != "" ] then JSON="{ \"body\": \"$1\" }" curl -d "$JSON" -ujbosstm-bot:$BOT_PASSWORD https://api.github.com/repos/$GIT_ACCOUNT/$GIT_REPO/issues/$PULL_NUMBER/c... else echo "Not a pull request, so not commenting" fi } PULL_NUMBER=$(echo $GIT_BRANCH | awk -F 'pull' '{ print $2 }' | awk -F '/' '{ print $2 }') PULL_DESCRIPTION=$(curl -ujbosstm-bot:$BOT_PASSWORD -s https://api.github.com/repos/$GIT_ACCOUNT/$GIT_REPO/pulls/$PULL_NUMBER) # https://developer.github.com/v4/reference/enum/commentauthorassociation/ PR_AUTHOR_MEMBERSHIP=$(echo $PULL_DESCRIPTION | sed 's/.*"author_association": "$[^,]*$".*/\1/') COMMENTS=$(curl -ujbosstm-bot:$BOT_PASSWORD -s https://api.github.com/repos/$GIT_ACCOUNT/$GIT_REPO/issues/$PULL_NUMBER/c...) MEMBERS_COMMENTS=$(printf '%s' "$COMMENTS" | awk '/"author_association"|"body"/ { if(/MEMBER|COLLABORATOR|OWNER/) {getline; print;} }') # if author of the PR is permitted or if the comment on the PR contains text 'TESTIT' written by one of the members if [[ ! $PR_AUTHOR_MEMBERSHIP =~ MEMBER|COLLABORATOR|OWNER|CONTRIBUTOR ]] && [[ ! $MEMBERS_COMMENTS =~ TESTIT ]]; then echo "Author of pull request '$PULL_NUMBER' is not member of github jbosstm organization or member comment needs to contain text 'TESTIT'" printf "membership of PR:\n%s\n" "$PR_AUTHOR_MEMBERSHIP" printf "members comments:\n%s\n" "$MEMBERS_COMMENTS" comment_on_pull ':warning: CI not started.\n\nAuthor is not the '$GIT_REPO' contributor, members of $GIT_ACCOUNT can write comment of text `TESTIT` to permit PR being run.' exit 0 fi ``` > Change the Narayana CI jobs to consider membership of PR author > --------------------------------------------------------------- > > Key: JBTM-2996 > URL: https://issues.jboss.org/browse/JBTM-2996 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Build System > Affects Versions: 5.7.2.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > It would be good to start using gihub webhooks instead of a poller jenkins cron job. > Configure the triggers in Jenkins and webhook on github and consider using the plugin > https://wiki.jenkins.io/display/JENKINS/GitHub+pull+request+builder+plugin -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 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 February 2018