August 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1453) Reinstate/review the numbers to detect performance regressions

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1453?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1453: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/672, https://github.com/jbosstm/narayana/pull/708 (was: https://github.com/jbosstm/narayana/pull/672) > Reinstate/review the numbers to detect performance regressions > -------------------------------------------------------------- > > Key: JBTM-1453 > URL: https://issues.jboss.org/browse/JBTM-1453 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.3 > > Original Estimate: 3 days > Remaining Estimate: 3 days > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2241) Removal of RecoveryHelpers fails silently if no scan is in progress

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2241?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2241: ----------------------------------- Status: Pull Request Sent (was: Open) > Removal of RecoveryHelpers fails silently if no scan is in progress > ------------------------------------------------------------------- > > Key: JBTM-2241 > URL: https://issues.jboss.org/browse/JBTM-2241 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.22, 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.23, 5.0.3 > > > There is some code in XARecoveryModule#removeXAResourceRecoveryHelper that defers removal of recovery helpers if a scan is in progress but skips the removal otherwise. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2238) Tooling does not expose CMR records

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2238?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2238: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/709 > Tooling does not expose CMR records > ----------------------------------- > > Key: JBTM-2238 > URL: https://issues.jboss.org/browse/JBTM-2238 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tooling > Affects Versions: 4.17.22, 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.23, 5.0.3 > > > CMR resources are not being exposed as MBeans via the (com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser) tooling. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2242) Misbehaving XAResources may delay deployments

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2242: -------------------------------------- Summary: Misbehaving XAResources may delay deployments Key: JBTM-2242 URL: https://issues.jboss.org/browse/JBTM-2242 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Application Server Integration Affects Versions: 5.0.2, 4.17.22 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 4.17.23, 5.0.3 Recovery scans can delay subsystem deployments because of contention on the lock XARecoveryModule#_xaResourceRecoveryHelpers: XARecoveryModule#resourceInitiatedRecoveryForRecoveryHelpers takes the lock and then makes calls to the resource which can potentially hang transiently. Meanwhile, deployments which register recovery helpers are delayed whilst waiting for the lock to be released (in XARecoveryModule#addXAResourceRecoveryHelper). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2241) Removal of RecoveryHelpers fails silently if no scan is in progress

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2241?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2241: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/710, https://github.com/jbosstm/narayana/pull/711 (was: https://github.com/jbosstm/narayana/pull/710) > Removal of RecoveryHelpers fails silently if no scan is in progress > ------------------------------------------------------------------- > > Key: JBTM-2241 > URL: https://issues.jboss.org/browse/JBTM-2241 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.22, 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.23, 5.0.3 > > > There is some code in XARecoveryModule#removeXAResourceRecoveryHelper that defers removal of recovery helpers if a scan is in progress but skips the removal otherwise. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2241) Removal of RecoveryHelpers fails silently if no scan is in progress

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2241: -------------------------------------- Summary: Removal of RecoveryHelpers fails silently if no scan is in progress Key: JBTM-2241 URL: https://issues.jboss.org/browse/JBTM-2241 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Recovery Affects Versions: 5.0.2, 4.17.22 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 4.17.23, 5.0.3 There is some code in XARecoveryModule#removeXAResourceRecoveryHelper that defers removal of recovery helpers if a scan is in progress but skips the removal otherwise. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2229) Issue with issue recovering AA with CMR, recovers OK but via orphan detection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2229?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2229: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1124861|https://bugzilla.redhat.com/show_bug.cgi?id=1124861] from POST to MODIFIED > Issue with issue recovering AA with CMR, recovers OK but via orphan detection > ----------------------------------------------------------------------------- > > Key: JBTM-2229 > URL: https://issues.jboss.org/browse/JBTM-2229 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Recovery > Affects Versions: 4.17.21, 5.0.2 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.22, 5.0.3 > > > The issue is with the CMR recovery module when it needs to update the underlying AA to modify it with the correct value from the CMR XIDS table. > If this AA does not have Serializable XARs, it will lead to the Xid being removed from XARM during getNewXAResource (via restore_state of the XARR). When the later AARM tries to recover the AA, it means a corresponding XAR for the XID cannot be located in the XARM by the XARR and an error message is reported. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2239) Update to use new Arquillian containers versioning

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2239?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed JBTM-2239. --------------------------------- Fix Version/s: (was: 5.0.3) Resolution: Rejected > Update to use new Arquillian containers versioning > -------------------------------------------------- > > Key: JBTM-2239 > URL: https://issues.jboss.org/browse/JBTM-2239 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > > Arquillian containers used to be versions based on WildFly release, e.g. 8.0.0.Final. However, they moved from that and currently are on 1.0.0.Alpha1. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2218) testSuspendResume(org.jboss.narayana.compensations.functional.compensationScoped.CompensationScopedTestRemote) failed

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2218?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2218: --------------------------------------- Yeah sure, assigning it to myself. > testSuspendResume(org.jboss.narayana.compensations.functional.compensationScoped.CompensationScopedTestRemote) failed > --------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2218 > URL: https://issues.jboss.org/browse/JBTM-2218 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Priority: Blocker > Fix For: 5.0.3 > > > Failing everywhere: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/127/... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/182/con... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/PROFILE=XTS,jdk=j... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/578/ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2218) testSuspendResume(org.jboss.narayana.compensations.functional.compensationScoped.CompensationScopedTestRemote) failed

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2218?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2218: ---------------------------------- Assignee: Gytis Trikleris (was: Paul Robinson) > testSuspendResume(org.jboss.narayana.compensations.functional.compensationScoped.CompensationScopedTestRemote) failed > --------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2218 > URL: https://issues.jboss.org/browse/JBTM-2218 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.0.3 > > > Failing everywhere: > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/127/... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/182/con... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/PROFILE=XTS,jdk=j... > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/578/ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 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 August 2014