December 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2810) Add a test to show RMERR handling

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2810?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2810. ------------------------------- > Add a test to show RMERR handling > --------------------------------- > > Key: JBTM-2810 > URL: https://issues.jboss.org/browse/JBTM-2810 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.4.1.Final > > > We had a question about why the log was now left when an XAR throws a HEURB. It was because if the forget fails we now remember the log. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2809) Include jboss-logging in the QA dependencies so it can be debugged easier

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2809?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2809. ------------------------------- > Include jboss-logging in the QA dependencies so it can be debugged easier > ------------------------------------------------------------------------- > > Key: JBTM-2809 > URL: https://issues.jboss.org/browse/JBTM-2809 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.4.1.Final > > > Unless jboss-logging is included you can't see tracing on the console when debugging issues -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2812) Retain a log if a forget call on a resource fails

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2812?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2812. ------------------------------- > Retain a log if a forget call on a resource fails > ------------------------------------------------- > > Key: JBTM-2812 > URL: https://issues.jboss.org/browse/JBTM-2812 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.4.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.4.1.Final > > > When we clear a heuristic from XAResourceRecord we call forget on the resource and then delete the record even if the forget operation fails. The preferred behaviour is to retain the record if the forget fails so that it can be reported via our tooling and so that we still have the option of later retrying the forget operation (also via the tooling). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2813) Cli operation for listing transactions returns not only transactions but participants too - for JTS inflow txn

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2813?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2813. ------------------------------- > Cli operation for listing transactions returns not only transactions but participants too - for JTS inflow txn > -------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2813 > URL: https://issues.jboss.org/browse/JBTM-2813 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.4.0.Final > Reporter: Ondra Chaloupka > Assignee: Michael Musgrove > Fix For: 5.4.1.Final > > Attachments: JcaInflowTransactionTestCase_rmerrWithRecovery_jts_server.log, tx-object-store_after-prepare.zip, tx-object-store_after-recover.zip > > > This is a follow-up from JBEAP-6307 where change JBTM-2767 (Allow JTS JCA imported transactions to have clearHeuristic called on their participants) was part of it. > That seems to bring wrong behavior of cli operation for listing transactions when JTS inflow txn is in use. Currently I do observe that operation [1] lists not only transactions as it should but there are listed participants of transaction as well - what is not expected. > When inflow transaction is prepared then I can see (the testcase contains only one prepared transaction at the time which consists of two test XAResources) > {code} > [standalone@localhost:42042 /] /subsystem=transactions/log-store=log-store:probe() > {"outcome" => "success"} > [standalone@localhost:42042 /] /subsystem=transactions/log-store=log-store:read-resource() > { > "outcome" => "success", > "result" => { > "expose-all-logs" => false, > "type" => "default", > "transactions" => { > "0:ffff7f000001:-f30b80c:58480e0a:2c" => undefined, > "0:ffff7f000001:-f30b80c:58480e0a:26" => undefined, > "0:ffff7f000001:-f30b80c:58480e0a:2f" => undefined > } > } > } > {code} > My test causes that one participant ends in heuristic state thus recovery is processed only for the second one. After recovery is processed the listing changes to > {code} > [standalone@localhost:42042 /] /subsystem=transactions/log-store=log-store:probe() > {"outcome" => "success"} > [standalone@localhost:42042 /] /subsystem=transactions/log-store=log-store:read-resource() > { > "outcome" => "success", > "result" => { > "expose-all-logs" => false, > "type" => "default", > "transactions" => { > "0:ffff7f000001:-f30b80c:58480e0a:26" => undefined, > "0:ffff7f000001:-f30b80c:58480e0a:2f" => undefined > } > } > } > {code} > I'm adding the content of {{tx-object-store}} at both phases and the {{server.log}} as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2808) Hang in getThreadId

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2808?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2808. ------------------------------- > Hang in getThreadId > ------------------- > > Key: JBTM-2808 > URL: https://issues.jboss.org/browse/JBTM-2808 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 5.4.1.Final > > > at java.util.WeakHashMap.expungeStaleEntries(WeakHashMap.java:341) > - locked <0x000000059f929538> (a java.lang.ref.ReferenceQueue) > at java.util.WeakHashMap.getTable(WeakHashMap.java:350) > at java.util.WeakHashMap.get(WeakHashMap.java:397) > at com.arjuna.ats.arjuna.utils.ThreadUtil.getThreadId(ThreadUtil.java:56) > No other locking, seems WeakHashMap needs synchronized. > https://docs.oracle.com/javase/7/docs/api/java/util/WeakHashMap.html > https://issues.jboss.org/browse/JBRULES-541?_sscc=t -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2807) StoreManager return always the same store

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2807?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2807. ------------------------------- > StoreManager return always the same store > ----------------------------------------- > > Key: JBTM-2807 > URL: https://issues.jboss.org/browse/JBTM-2807 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.4.0.Final > Reporter: Ivan Straka > Assignee: Ivan Straka > Fix For: 5.4.1.Final > > > StoreManager.get*Store() returns always the same store even after changing it via BeanPopulator. > Problem is that StoreManager.actionStore, StoreManager.stateStore, StoreManager.communicationStore won't change after they are set for the first time. > https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes... > this method should null stores. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2804) ObjStoreBrowserTest.java can miss a recovery scan

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2804?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2804. ------------------------------- > ObjStoreBrowserTest.java can miss a recovery scan > ------------------------------------------------- > > Key: JBTM-2804 > URL: https://issues.jboss.org/browse/JBTM-2804 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.4.1.Final > > > As the ObjStoreBrowserTest.java uses a socket to ask for recovery from a threaded recovery manager it is possible that the recovery manager is just completing a scan and so the state the test expects will not be satisfied. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2803) compareHierarchies traceln's wrong elements

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2803?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2803. ------------------------------- > compareHierarchies traceln's wrong elements > ------------------------------------------- > > Key: JBTM-2803 > URL: https://issues.jboss.org/browse/JBTM-2803 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.4.1.Final > > > If compareHierarchies is called (only done in trace iirc) then the right elements are compared but if they are not equal the wrong elements are compared IOOBE are possible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2801) ObjectStoreTest.java assumes that Uids are returned in order which is not guaranteed

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2801?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2801. ------------------------------- > ObjectStoreTest.java assumes that Uids are returned in order which is not guaranteed > ------------------------------------------------------------------------------------ > > Key: JBTM-2801 > URL: https://issues.jboss.org/browse/JBTM-2801 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.4.1.Final > > > The object store API does not make guarantees about the order -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2802) AtomicObject3.java hammer test hard to debug

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2802?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2802. ------------------------------- > AtomicObject3.java hammer test hard to debug > -------------------------------------------- > > Key: JBTM-2802 > URL: https://issues.jboss.org/browse/JBTM-2802 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.4.1.Final > > > As the test outputs to console with println and has many many threads it is too hard to debug. Use log4j. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 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 December 2016