October 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2749) Add an SPI method to lookup imported transactions by Xid

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2749?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2749: -------------------------------- Fix Version/s: 5.2.19.Final 4.17.37 > Add an SPI method to lookup imported transactions by Xid > -------------------------------------------------------- > > Key: JBTM-2749 > URL: https://issues.jboss.org/browse/JBTM-2749 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JCA, SPI > Affects Versions: 5.3.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 4.17.37, 5.2.19.Final, 5.3.5.Final > > > When EJB remoting sees an incoming transaction it needs to determine whether it is one that the TM already knows about and should just resume it or if it needs to start a new subordinate transaction for it on this node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2749) Add an SPI method to lookup imported transactions by Xid

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2749?page=com.atlassian.jira.plugin.... ] Tom Jenkinson closed JBTM-2749. ------------------------------- Resolution: Done > Add an SPI method to lookup imported transactions by Xid > -------------------------------------------------------- > > Key: JBTM-2749 > URL: https://issues.jboss.org/browse/JBTM-2749 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JCA, SPI > Affects Versions: 5.3.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.3.5.Final, 5.2.19.Final, 4.17.37 > > > When EJB remoting sees an incoming transaction it needs to determine whether it is one that the TM already knows about and should just resume it or if it needs to start a new subordinate transaction for it on this node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2739) Add a CI job for testing jboss-transaction-spi

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2739?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2739: -------------------------------- Fix Version/s: 5.2.19.Final > Add a CI job for testing jboss-transaction-spi > ---------------------------------------------- > > Key: JBTM-2739 > URL: https://issues.jboss.org/browse/JBTM-2739 > Project: JBoss Transaction Manager > Issue Type: Task > Components: SPI > Affects Versions: 5.3.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.2.19.Final, 5.next > > > We need a CI job to test that narayana works with the latest jboss-transaction-spi and this should include PRs as well as master. > In addition, the two projects duplicate tests so the the duplicates need removing from narayana (but only after we have added this CI testing). > Note that jboss-transaction-spi has a test dependency on the last released stable version of narayana so that dependency would need to changed to the version of our current SNAPSHOT for these new proposed CI jobs to be useful. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2749) Add an SPI method to lookup imported transactions by Xid

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2749?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-2749: --------------------------------- > Add an SPI method to lookup imported transactions by Xid > -------------------------------------------------------- > > Key: JBTM-2749 > URL: https://issues.jboss.org/browse/JBTM-2749 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JCA, SPI > Affects Versions: 5.3.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.3.5.Final > > > When EJB remoting sees an incoming transaction it needs to determine whether it is one that the TM already knows about and should just resume it or if it needs to start a new subordinate transaction for it on this node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2749) Add an SPI method to lookup imported transactions by Xid

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2749?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2749: ----------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1383572|https://bugzilla.redhat.com/show_bug.cgi?id=1383572] from POST to MODIFIED > Add an SPI method to lookup imported transactions by Xid > -------------------------------------------------------- > > Key: JBTM-2749 > URL: https://issues.jboss.org/browse/JBTM-2749 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JCA, SPI > Affects Versions: 5.3.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.3.5.Final > > > When EJB remoting sees an incoming transaction it needs to determine whether it is one that the TM already knows about and should just resume it or if it needs to start a new subordinate transaction for it on this node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2749) Add an SPI method to lookup imported transactions by Xid

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2749?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2749: ----------------------------------------------- Peter Palaga <ppalaga(a)redhat.com> changed the Status of [bug 1383572|https://bugzilla.redhat.com/show_bug.cgi?id=1383572] from MODIFIED to POST > Add an SPI method to lookup imported transactions by Xid > -------------------------------------------------------- > > Key: JBTM-2749 > URL: https://issues.jboss.org/browse/JBTM-2749 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JCA, SPI > Affects Versions: 5.3.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.3.5.Final > > > When EJB remoting sees an incoming transaction it needs to determine whether it is one that the TM already knows about and should just resume it or if it needs to start a new subordinate transaction for it on this node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2749) Add an SPI method to lookup imported transactions by Xid

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-2749?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-2749: ----------------------------------------------- Radovan Netuka <rnetuka(a)redhat.com> changed the Status of [bug 1383572|https://bugzilla.redhat.com/show_bug.cgi?id=1383572] from ASSIGNED to POST > Add an SPI method to lookup imported transactions by Xid > -------------------------------------------------------- > > Key: JBTM-2749 > URL: https://issues.jboss.org/browse/JBTM-2749 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JCA, SPI > Affects Versions: 5.3.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.3.5.Final > > > When EJB remoting sees an incoming transaction it needs to determine whether it is one that the TM already knows about and should just resume it or if it needs to start a new subordinate transaction for it on this node. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2774) Leak when imported subordinate transactions are rolled back by reaper before remote reaper

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2774?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #1078 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Leak when imported subordinate transactions are rolled back by reaper before remote reaper > ------------------------------------------------------------------------------------------ > > Key: JBTM-2774 > URL: https://issues.jboss.org/browse/JBTM-2774 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > When using the EJB remoting transport that layers over the top of JCA it is possible for a race condition between the two reapers. > Normally you have server 1 and server 2. Each of these insert the TwoPhaseCoordinator in their TransactionReaper. If the TransactionReaper in server 2 fires first then it will rollback the TPC. > When server 1 Reaper EJB remoting transport fires it will try to rollback at server 2 also and it is this that should be safe to remove the transactionImple reference. > At the time of reporting the reference is not removed though and so the reference to the TransactionImple is not removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2774) Leak when imported subordinate transactions are rolled back by reaper before remote reaper

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2774: ----------------------------------- Summary: Leak when imported subordinate transactions are rolled back by reaper before remote reaper Key: JBTM-2774 URL: https://issues.jboss.org/browse/JBTM-2774 Project: JBoss Transaction Manager Issue Type: Bug Components: Application Server Integration Reporter: Tom Jenkinson Assignee: Tom Jenkinson When using the EJB remoting transport that layers over the top of JCA it is possible for a race condition between the two reapers. Normally you have server 1 and server 2. Each of these insert the TwoPhaseCoordinator in their TransactionReaper. If the TransactionReaper in server 2 fires first then it will rollback the TPC. When server 1 Reaper EJB remoting transport fires it will try to rollback at server 2 also and it is this that should be safe to remove the transactionImple reference. At the time of reporting the reference is not removed though and so the reference to the TransactionImple is not removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2773) NPE when trying delete heuristic transaction (with CMR resource) from JDBC tx log-store

by Daniel Simko (JIRA)

[ https://issues.jboss.org/browse/JBTM-2773?page=com.atlassian.jira.plugin.... ] Daniel Simko moved JBEAP-6468 to JBTM-2773: ------------------------------------------- Project: JBoss Transaction Manager (was: JBoss Enterprise Application Platform) Key: JBTM-2773 (was: JBEAP-6468) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Transaction Core (was: Transactions) Affects Version/s: 5.3.5.Final (was: 7.1.0.DR6) Affects Testing: (was: Regression) > NPE when trying delete heuristic transaction (with CMR resource) from JDBC tx log-store > --------------------------------------------------------------------------------------- > > Key: JBTM-2773 > URL: https://issues.jboss.org/browse/JBTM-2773 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.3.5.Final > Reporter: Daniel Simko > Assignee: Tom Jenkinson > Priority: Critical > > Part of the test is cleaning tx log-store: > {code} > 14:36:46,747 ERROR [org.jboss.as.test.jbossts.base.setup.operations.TMOperations] (main) Management operation { > "operation" => "delete", > "address" => [ > ("subsystem" => "transactions"), > ("log-store" => "log-store"), > ("transactions" => "0:ffff7f000001:-475b5c9c:5804af44:31") > ] > } failed: { > "outcome" => "failed", > "failure-description" => "java.lang.NullPointerException", > "rolled-back" => true > } > {code} > but fails with NPE. Server log: > {code} > 2016-10-17 14:36:42,798 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) InputObjectState::InputObjectState() > 2016-10-17 14:36:42,798 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) OutputObjectState::OutputObjectState() > 2016-10-17 14:36:43,140 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) StateManager::StateManager( 0:ffff7f000001:-475b5c9c:5804af44:31 ) > 2016-10-17 14:36:43,140 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) BasicAction::BasicAction(0:ffff7f000001:-475b5c9c:5804af44:31) > 2016-10-17 14:36:43,141 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) BasicAction::activate() for action-id 0:ffff7f000001:-475b5c9c:5804af44:31 > 2016-10-17 14:36:43,308 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) InputObjectState::InputObjectState(0:ffff7f000001:-475b5c9c:5804af44:31, StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction) > 2016-10-17 14:36:43,474 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) BasicAction::restore_state () > 2016-10-17 14:36:43,475 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) StateManager.unpackHeader for object-id 0:ffff7f000001:-475b5c9c:5804af44:31 birth-date 1476707800081 > 2016-10-17 14:36:43,475 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) Unpacked a 463 record > 2016-10-17 14:36:43,475 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) HeuristicList - Unpacked heuristic list size of 1 > 2016-10-17 14:36:43,475 WARN [com.arjuna.ats.arjuna] (management-handler-thread - 4) Transaction 0:ffff7f000001:-475b5c9c:5804af44:31 has 1 heuristic participant(s)! > 2016-10-17 14:36:43,475 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) HeuristicList - Unpacked a 50 record > 2016-10-17 14:36:43,475 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) StateManager::StateManager( 0:0:0:0:0 ) > 2016-10-17 14:36:43,475 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) AbstractRecord::AbstractRecord () - crash recovery constructor > 2016-10-17 14:36:43,475 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) CommitMarkableResourceRecord.CommitMarkableResourceRecord (), record id=-8000000000000000:-8000000000000000:-80000000:-80000000:-80000000 > 2016-10-17 14:36:43,475 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) unpack: java:jboss/xa-datasources/CrashRecoveryDS > 2016-10-17 14:36:43,475 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) unpack: < formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:-475b5c9c:5804af44:31, node_name=1, branch_uid=0:ffff7f000001:-475b5c9c:5804af44:37, subordinatenodename=null, eis_name=java:jboss/xa-datasources/CrashRecoveryDS > > 2016-10-17 14:36:43,476 TRACE [com.arjuna.ats.jta] (management-handler-thread - 4) TransactionSynchronizationRegistryImple.getTransactionKey > 2016-10-17 14:36:43,476 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) Attempting to delete number of entries: 2 > 2016-10-17 14:36:43,991 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) CommitMarkableResourceRecordRecoveryModule::periodicWorkFirstPass > 2016-10-17 14:36:43,991 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) CommitMarkableResourceRecordRecoveryModule::connecting to: java:jboss/xa-datasources/CrashRecoveryDS > 2016-10-17 14:36:43,991 TRACE [com.arjuna.ats.jta] (management-handler-thread - 4) TransactionSynchronizationRegistryImple.getTransactionKey > 2016-10-17 14:36:44,334 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) InputObjectState::InputObjectState() > 2016-10-17 14:36:44,335 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) OutputObjectState::OutputObjectState() > 2016-10-17 14:36:44,669 DEBUG [com.arjuna.ats.arjuna] (management-handler-thread - 4) processing /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction transactions > 2016-10-17 14:36:44,669 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) InputObjectState::InputObjectState() > 2016-10-17 14:36:44,669 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) OutputObjectState::OutputObjectState() > 2016-10-17 14:36:45,002 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) InputObjectState::InputObjectState() > 2016-10-17 14:36:45,002 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) OutputObjectState::OutputObjectState() > 2016-10-17 14:36:45,838 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) InputObjectState::InputObjectState(0:ffff7f000001:-475b5c9c:5804af44:31, StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction) > 2016-10-17 14:36:46,004 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) StateManager::StateManager( 0:ffff7f000001:-475b5c9c:5804af44:31 ) > 2016-10-17 14:36:46,004 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) BasicAction::BasicAction(0:ffff7f000001:-475b5c9c:5804af44:31) > 2016-10-17 14:36:46,005 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) StateManager.unpackHeader for object-id 0:ffff7f000001:-475b5c9c:5804af44:31 birth-date 1476707800081 > 2016-10-17 14:36:46,005 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) wasCommitted< formatId=131077, gtrid_length=29, bqual_length=36, tx_uid=0:ffff7f000001:-475b5c9c:5804af44:31, node_name=1, branch_uid=0:ffff7f000001:-475b5c9c:5804af44:37, subordinatenodename=null, eis_name=java:jboss/xa-datasources/CrashRecoveryDS > null > 2016-10-17 14:36:46,005 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) RecordList::insert(RecordList: empty) : appending /StateManager/AbstractRecord/CommitMarkableResourceRecord for -8000000000000000:-8000000000000000:-80000000:-80000000:-80000000 > 2016-10-17 14:36:46,005 WARN [com.arjuna.ats.arjuna] (management-handler-thread - 4) Transaction 0:ffff7f000001:-475b5c9c:5804af44:31 restored heuristic participant com.arjuna.ats.internal.jta.resources.arjunacore.CommitMarkableResourceRecord@2493dae0 > 2016-10-17 14:36:46,005 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) HeuristicList - Unpacked a 463 record > 2016-10-17 14:36:46,005 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) Restored action status of ActionStatus.COMMITTED 7 > 2016-10-17 14:36:46,005 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) Restored action type Top-level 0 > 2016-10-17 14:36:46,005 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) Restored heuristic decision of TwoPhaseOutcome.HEURISTIC_ROLLBACK 3 > 2016-10-17 14:36:46,005 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) StateManager::StateManager( 0:ffff7f000001:-475b5c9c:5804af44:31 ) > 2016-10-17 14:36:46,174 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) InputObjectState::InputObjectState(0:ffff7f000001:-475b5c9c:5804af44:31, StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction) > 2016-10-17 14:36:46,344 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) StateManager::activate( null) for object-id 0:0:0:0:0 > 2016-10-17 14:36:46,345 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) StateManager::setupStore ( null ) > 2016-10-17 14:36:46,682 WARN [com.arjuna.ats.arjuna] (management-handler-thread - 4) ARJUNA012035: Activate of object with id = 0:0:0:0:0 and type /StateManager/AbstractRecord/CommitMarkableResourceRecord unexpectedly failed > 2016-10-17 14:36:46,682 TRACE [com.arjuna.ats.arjuna] (management-handler-thread - 4) Registering: jboss.jta:type=ObjectStore,itype=StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction,uid=0_ffff7f000001_-475b5c9c_5804af44_31 > 2016-10-17 14:36:46,682 DEBUG [com.arjuna.ats.arjuna] (management-handler-thread - 4) registering bean jboss.jta:type=ObjectStore,itype=StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction,uid=0_ffff7f000001_-475b5c9c_5804af44_31 > 2016-10-17 14:36:46,683 DEBUG [com.arjuna.ats.arjuna] (management-handler-thread - 4) registering bean jboss.jta:type=ObjectStore,itype=StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction,uid=0_ffff7f000001_-475b5c9c_5804af44_31,puid=-8000000000000000_-8000000000000000_-80000000_-80000000_-80000000 > {code} > Test passed for EAP 7.1.0.DR5 but failed for EAP 7.1.0.DR6. For another types of log-store (standard file based, activemq artemis journal) test passed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues October 2016