November 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2274) Create separate assumed complete type for heuristic transactions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2274?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2274: ----------------------------------------------- Hayk Hovsepyan <hhovsepy(a)redhat.com> changed the Status of [bug 1080140|https://bugzilla.redhat.com/show_bug.cgi?id=1080140] from ON_QA to VERIFIED > Create separate assumed complete type for heuristic transactions > ---------------------------------------------------------------- > > Key: JBTM-2274 > URL: https://issues.jboss.org/browse/JBTM-2274 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 4.17.24, 5.0.4 > > > Currently all JTS transaction records are moved to assumed complete store after 3 recovery tries. This is not good if the transaction has a heuristic outcome. It leads to the heuristic participant being rolled back, because recovery coordinator cannot see the log record after the move. > Creating separate locations for such heuristic transactions and checking their status during replay_completion would solve the problem. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2308) JTS participants are not showing up in the tooling

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTM-2308: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1168973 > JTS participants are not showing up in the tooling > -------------------------------------------------- > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.4 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I've marked the JIRA as a bug rather than an enhancement since it used to work (I'll fix the missing test at the same time). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2308) JTS participants are not showing up in the tooling

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2308: ----------------------------------------------- tom.jenkinson(a)redhat.com changed the Status of [bug 1168973|https://bugzilla.redhat.com/show_bug.cgi?id=1168973] from NEW to ASSIGNED > JTS participants are not showing up in the tooling > -------------------------------------------------- > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.0.4 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I've marked the JIRA as a bug rather than an enhancement since it used to work (I'll fix the missing test at the same time). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-1939) Consider using awestruct to develop http://narayana.io

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1939?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1939. --------------------------------- Resolution: Done > Consider using awestruct to develop http://narayana.io > ------------------------------------------------------ > > Key: JBTM-1939 > URL: https://issues.jboss.org/browse/JBTM-1939 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.4 > > > Awestruct appears to be a powerful and flexible tool to develop websites with. This task is to research the capabilities of the tool and determine if the benefits of awestruct apply to our website. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2279: ----------------------------------------------- tom.jenkinson(a)redhat.com changed the Status of [bug 1168836|https://bugzilla.redhat.com/show_bug.cgi?id=1168836] from ASSIGNED to MODIFIED > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.25, 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2302: ----------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 1165700|https://bugzilla.redhat.com/show_bug.cgi?id=1165700] from ASSIGNED to MODIFIED > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.25, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2279) Provide a way to allow overriding of a set CheckedActionFactory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2279?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2279: ----------------------------------------------- tom.jenkinson(a)redhat.com changed the Status of [bug 1168836|https://bugzilla.redhat.com/show_bug.cgi?id=1168836] from NEW to ASSIGNED > Provide a way to allow overriding of a set CheckedActionFactory > --------------------------------------------------------------- > > Key: JBTM-2279 > URL: https://issues.jboss.org/browse/JBTM-2279 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.25, 5.0.4 > > > Out of the box the BasicAction caches the reference to the checkedactionfactory and so if a users classpath is not available to narayana there is no way for a user to provide a CAF to Narayana. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2302) Tooling can create two mbeans for a CMR record

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2302?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2302: ----------------------------------------------- tom.jenkinson(a)redhat.com changed the Status of [bug 1165700|https://bugzilla.redhat.com/show_bug.cgi?id=1165700] from MODIFIED to ASSIGNED > Tooling can create two mbeans for a CMR record > ---------------------------------------------- > > Key: JBTM-2302 > URL: https://issues.jboss.org/browse/JBTM-2302 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Environment: JDK8 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.25, 5.0.4 > > > The ObjStoreBrowser.probe() operation creates MBeans corresponding to object store records. CMR records move between AtomicAction (AA) and AtomicActionConnectable (AAC). When running QA EAP tests on JDK8 a test fails because it detects the creation of two MBeans for each one - this is an error because: > - the record is moved between the locations so there should only ever be one bean representation of it; > - it causes two nodes with the same id (we use the record uid for the node id) to be added to the transaction subsystem management model > The problem is happening because the probe routine first creates new beans for new records and then destroys beans for records that are no longer present. This means that there is a small window where we have 2 beans for the same uid. > The fix is to do the bean remove before adding new beans for new records. > It is unclear why the bug only happens on JDK8. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2284) XID.toString broken: indexing mistake in array

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2284?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2284. ------------------------------- > XID.toString broken: indexing mistake in array > ---------------------------------------------- > > Key: JBTM-2284 > URL: https://issues.jboss.org/browse/JBTM-2284 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 4.17.15 > Environment: EAP 6.2.4 with JBoss JTS module in version 4.17.15 > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > Fix For: 4.17.24 > > > com.arjuna.ats.internal.jta.xa.XID > > public String toString () > { > //... > stringBuilder.append(", "); > for (int i = 0; i < bqual_length; i++) { > stringBuilder.append(gtrid_length+data[i]); > } > //... > } > > correct: stringBuilder.append(data[i+gtrid_length]); > The result is, that the Xid instances logged in log files are corrupted and multiple different Xid share the same String representation, which makes the logging information unusable -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2271) ConcurrentModificationException exception raised by CMR Recovery module first pass

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2271?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2271. ------------------------------- > ConcurrentModificationException exception raised by CMR Recovery module first pass > ---------------------------------------------------------------------------------- > > Key: JBTM-2271 > URL: https://issues.jboss.org/browse/JBTM-2271 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.24, 5.0.3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2014