March 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3266) BlackTie CI hang

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3266?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3266: ----------------------------------- Description: CI BlackTie CSTest test ended in an infinite loop trying to recover a REST-AT record: Running org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest [0m21:59:47,500 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_.testsui1 [0m[0m21:59:47,677 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 111) AMQ221003: trying to deploy queue jms.queue.BTR_BAR [0m[0m21:59:47,828 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_TestTPCall [0m[0m21:59:54,876 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_.testsui1 [0m[0m21:59:55,050 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 111) AMQ221003: trying to deploy queue jms.queue.BTR_BAR [0m[0m21:59:55,221 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_TestTPCall [0m[31m21:59:56,295 ERROR [org.codehaus.stomp.tcp.TcpTransport] (StompConnect Transport: tcp:///127.0.0.1:36366) Caught an exception: null: java.lang.NullPointerException at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:104) at java.lang.Thread.run(Thread.java:748) [0m[33m22:00:24,789 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffffac11000d:-279d1482:5e62c04e:84 has 1 heuristic participant(s)! [0m[0m22:00:24,789 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a9%3a887386/terminate [0m[33m22:00:24,789 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffffac11000d:-279d1482:5e62c04e:84 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord@2798da8b [0m[33m22:00:24,791 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffffac11000d:-279d1482:5e62c04e:8b has 1 heuristic participant(s)! [0m[0m22:00:24,791 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a12%3a941281/terminate [0m[33m22:00:24,791 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffffac11000d:-279d1482:5e62c04e:8b restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord@7941fa30 etc (for ever) was: CI BlackTie CSTest test ended in an infinite loop trying to recover a REST-AT record: Running org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest [0m21:59:47,500 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_.testsui1 [0m[0m21:59:47,677 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 111) AMQ221003: trying to deploy queue jms.queue.BTR_BAR [0m[0m21:59:47,828 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_TestTPCall [0m[0m21:59:54,876 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_.testsui1 [0m[0m21:59:55,050 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 111) AMQ221003: trying to deploy queue jms.queue.BTR_BAR [0m[0m21:59:55,221 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_TestTPCall [0m[31m21:59:56,295 ERROR [org.codehaus.stomp.tcp.TcpTransport] (StompConnect Transport: tcp:///127.0.0.1:36366) Caught an exception: null: java.lang.NullPointerException at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:104) at java.lang.Thread.run(Thread.java:748) > BlackTie CI hang > ---------------- > > Key: JBTM-3266 > URL: https://issues.redhat.com/browse/JBTM-3266 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Assignee: Zheng Feng > Priority: Major > Fix For: 5.next > > Attachments: tx-object-store.tar > > > CI BlackTie CSTest test ended in an infinite loop trying to recover a REST-AT record: > Running org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest > [0m21:59:47,500 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > [0m[0m21:59:47,677 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 111) AMQ221003: trying to deploy queue jms.queue.BTR_BAR > [0m[0m21:59:47,828 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > [0m[0m21:59:54,876 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > [0m[0m21:59:55,050 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 111) AMQ221003: trying to deploy queue jms.queue.BTR_BAR > [0m[0m21:59:55,221 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > [0m[31m21:59:56,295 ERROR [org.codehaus.stomp.tcp.TcpTransport] (StompConnect Transport: tcp:///127.0.0.1:36366) Caught an exception: null: java.lang.NullPointerException > at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:104) > at java.lang.Thread.run(Thread.java:748) > [0m[33m22:00:24,789 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffffac11000d:-279d1482:5e62c04e:84 has 1 heuristic participant(s)! > [0m[0m22:00:24,789 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a39%3a9%3a887386/terminate > [0m[33m22:00:24,789 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffffac11000d:-279d1482:5e62c04e:84 restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord@2798da8b > [0m[33m22:00:24,791 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffffac11000d:-279d1482:5e62c04e:8b has 1 heuristic participant(s)! > [0m[0m22:00:24,791 INFO [org.jboss.jbossts.star.resource.RESTRecord] (Periodic Recovery) restore_state http://127.0.0.1:8888/xid/131077%3a102%3a0%3a42%3a12%3a941281/terminate > [0m[33m22:00:24,791 WARN [com.arjuna.ats.arjuna] (Periodic Recovery) Transaction 0:ffffac11000d:-279d1482:5e62c04e:8b restored heuristic participant org.jboss.jbossts.star.resource.RESTRecord@7941fa30 > etc (for ever) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3266) BlackTie CI hang

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3266?page=com.atlassian.jira.plugin... ] Michael Musgrove commented on JBTM-3266: ---------------------------------------- The attached file is the object store that contains the 4 records with a single unrecoverable heuristic participant. > BlackTie CI hang > ---------------- > > Key: JBTM-3266 > URL: https://issues.redhat.com/browse/JBTM-3266 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Assignee: Zheng Feng > Priority: Major > Fix For: 5.next > > Attachments: tx-object-store.tar > > > CI BlackTie CSTest test ended in an infinite loop trying to recover a REST-AT record: > Running org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest > [0m21:59:47,500 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > [0m[0m21:59:47,677 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 111) AMQ221003: trying to deploy queue jms.queue.BTR_BAR > [0m[0m21:59:47,828 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > [0m[0m21:59:54,876 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > [0m[0m21:59:55,050 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 111) AMQ221003: trying to deploy queue jms.queue.BTR_BAR > [0m[0m21:59:55,221 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > [0m[31m21:59:56,295 ERROR [org.codehaus.stomp.tcp.TcpTransport] (StompConnect Transport: tcp:///127.0.0.1:36366) Caught an exception: null: java.lang.NullPointerException > at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:104) > at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3266) BlackTie CI hang

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3266?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3266: ----------------------------------- Attachment: tx-object-store.tar > BlackTie CI hang > ---------------- > > Key: JBTM-3266 > URL: https://issues.redhat.com/browse/JBTM-3266 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Assignee: Zheng Feng > Priority: Major > Fix For: 5.next > > Attachments: tx-object-store.tar > > > CI BlackTie CSTest test ended in an infinite loop trying to recover a REST-AT record: > Running org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest > [0m21:59:47,500 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > [0m[0m21:59:47,677 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 111) AMQ221003: trying to deploy queue jms.queue.BTR_BAR > [0m[0m21:59:47,828 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > [0m[0m21:59:54,876 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_.testsui1 > [0m[0m21:59:55,050 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 111) AMQ221003: trying to deploy queue jms.queue.BTR_BAR > [0m[0m21:59:55,221 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_TestTPCall > [0m[31m21:59:56,295 ERROR [org.codehaus.stomp.tcp.TcpTransport] (StompConnect Transport: tcp:///127.0.0.1:36366) Caught an exception: null: java.lang.NullPointerException > at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:104) > at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3266) BlackTie CI hang

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3266: -------------------------------------- Summary: BlackTie CI hang Key: JBTM-3266 URL: https://issues.redhat.com/browse/JBTM-3266 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie Affects Versions: 5.10.3.Final Reporter: Michael Musgrove Assignee: Zheng Feng Fix For: 5.next Attachments: tx-object-store.tar CI BlackTie CSTest test ended in an infinite loop trying to recover a REST-AT record: Running org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest [0m21:59:47,500 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_.testsui1 [0m[0m21:59:47,677 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 111) AMQ221003: trying to deploy queue jms.queue.BTR_BAR [0m[0m21:59:47,828 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_TestTPCall [0m[0m21:59:54,876 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_.testsui1 [0m[0m21:59:55,050 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 111) AMQ221003: trying to deploy queue jms.queue.BTR_BAR [0m[0m21:59:55,221 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 110) AMQ221003: trying to deploy queue jms.queue.BTR_TestTPCall [0m[31m21:59:56,295 ERROR [org.codehaus.stomp.tcp.TcpTransport] (StompConnect Transport: tcp:///127.0.0.1:36366) Caught an exception: null: java.lang.NullPointerException at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:104) at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3265) Failing LRA test FailingParticipantCallsIT#testFailingAfterLRA

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3265?page=com.atlassian.jira.plugin... ] Issue was automatically transitioned when Michael Musgrove created pull request #1565 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Failing LRA test FailingParticipantCallsIT#testFailingAfterLRA > -------------------------------------------------------------- > > Key: JBTM-3265 > URL: https://issues.redhat.com/browse/JBTM-3265 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > FailingParticipantCallsIT.testFailingAfterLRA fails regularly on CI -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3257) On recovery scan the NullPointerException can be thrown when client side exits prior DONE is delivered from server

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3257?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3257: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next Resolution: Done > On recovery scan the NullPointerException can be thrown when client side exits prior DONE is delivered from server > ------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-3257 > URL: https://issues.redhat.com/browse/JBTM-3257 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.10.3.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > Fix For: 5.next > > > When triggering recovery on recovery listener it could happen the client side starts sending but does not finish with a new line. For the recovery socket reader it's as there was called no {{flush}} - it still waits for get all information. But meanwhile the socket is closed and buffer reader at the server side gets {{null}} at that poing. > In such case a {{NullPointerException}} can be thrown from the Narayana code. > {code} > WARN [com.arjuna.ats.arjuna] (Server.Connection:127.0.0.1:37264) ARJUNA012338: Other Exception:: java.lang.NullPointerException > at com.arjuna.ats.internal.arjuna.recovery.WorkerService.doWork(WorkerService.java:66) > at com.arjuna.ats.internal.arjuna.recovery.Connection.run(Connection.java:88) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3259) Race condition on terminating recovery manager and socket call when scanning is underway

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3259?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3259: ----------------------------------- Affects Version/s: 5.10.3.Final > Race condition on terminating recovery manager and socket call when scanning is underway > ---------------------------------------------------------------------------------------- > > Key: JBTM-3259 > URL: https://issues.redhat.com/browse/JBTM-3259 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.10.3.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.next > > > There is a race condition which causes a recovery to be stuck. > This happens at time when recovery manager is running and there is a try to run a socket {{SCAN}} command or a {{RecoveryDriver}} api is about to use to start scan. > When the recovery manager is terminated then it can happen that the {{Listnener}} asks for scan to be done, then recovery manager is terminated and the Listener then stops waiting forever. > At that time there is already terminated recovery manager and Listener just waits for being notified that scan finished (we talk about {{SYNC}} call). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3259) Race condition on terminating recovery manager and socket call when scanning is underway

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3259?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3259: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next Resolution: Done > Race condition on terminating recovery manager and socket call when scanning is underway > ---------------------------------------------------------------------------------------- > > Key: JBTM-3259 > URL: https://issues.redhat.com/browse/JBTM-3259 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.10.3.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.next > > > There is a race condition which causes a recovery to be stuck. > This happens at time when recovery manager is running and there is a try to run a socket {{SCAN}} command or a {{RecoveryDriver}} api is about to use to start scan. > When the recovery manager is terminated then it can happen that the {{Listnener}} asks for scan to be done, then recovery manager is terminated and the Listener then stops waiting forever. > At that time there is already terminated recovery manager and Listener just waits for being notified that scan finished (we talk about {{SYNC}} call). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3259) Race condition on terminating recovery manager and socket call when scanning is underway

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3259?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3259: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/1561 > Race condition on terminating recovery manager and socket call when scanning is underway > ---------------------------------------------------------------------------------------- > > Key: JBTM-3259 > URL: https://issues.redhat.com/browse/JBTM-3259 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.10.3.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.next > > > There is a race condition which causes a recovery to be stuck. > This happens at time when recovery manager is running and there is a try to run a socket {{SCAN}} command or a {{RecoveryDriver}} api is about to use to start scan. > When the recovery manager is terminated then it can happen that the {{Listnener}} asks for scan to be done, then recovery manager is terminated and the Listener then stops waiting forever. > At that time there is already terminated recovery manager and Listener just waits for being notified that scan finished (we talk about {{SYNC}} call). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3259) Race condition on terminating recovery manager and socket call when scanning is underway

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3259?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3259: ----------------------------------- Status: Pull Request Sent (was: Open) https://github.com/jbosstm/narayana/pull/1561 > Race condition on terminating recovery manager and socket call when scanning is underway > ---------------------------------------------------------------------------------------- > > Key: JBTM-3259 > URL: https://issues.redhat.com/browse/JBTM-3259 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.10.3.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.next > > > There is a race condition which causes a recovery to be stuck. > This happens at time when recovery manager is running and there is a try to run a socket {{SCAN}} command or a {{RecoveryDriver}} api is about to use to start scan. > When the recovery manager is terminated then it can happen that the {{Listnener}} asks for scan to be done, then recovery manager is terminated and the Listener then stops waiting forever. > At that time there is already terminated recovery manager and Listener just waits for being notified that scan finished (we talk about {{SYNC}} call). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 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 2020