June 2017 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2905) JCAServerTransactionHeaderReader is placed under tests package which makes troubles for tooling

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2905?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2905: -------------------------------- Fix Version/s: 5.5.24.Final > JCAServerTransactionHeaderReader is placed under tests package which makes troubles for tooling > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2905 > URL: https://issues.jboss.org/browse/JBTM-2905 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.6.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.next, 5.5.24.Final > > > The class {{JCAServerTransactionHeaderReader}} is placed under package {{com.hp.mwtests.ts.jta.jts.tools.}} which means is not available during runtime of tooling. As the header reader is used by {{com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser}} it brings situations where the record can't be loaded by tooling. The browser seems to be used by Expiry Scanner and that suffers by that fact. > The WFLY start sequence contains info of not possible to load the reader when the object store contains some unfinished jca subordinate transaction. > {code} > INFO [com.arjuna.ats.arjuna] (MSC service thread 1-4) ARJUNA012389: OSB: Error constructing record header reader: com.hp.mwtests.ts.jta.jts.tools.JCAServerTransactionHeaderReader from [Module "org.jboss.jts" from local module loader @6b419da (finder: local module finder @3b2da18f (roots: /home/ochaloup/Transactions/eap-tests-transactions/jbossts/target/jbossas-jbossts/modules,/home/ochaloup/jboss/jboss-eap-7.1.0.DR19/modules,/home/ochaloup/jboss/jboss-eap-7.1.0.DR19/modules/system/layers/base,/home/ochaloup/Transactions/eap-tests-transactions/jbossts/target/jbossas-jbossts/modules))] > {code} > The point is to move the jca reader under jts tooling package to be compiled and distributed in the {{jts}} jar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2907) Implement doRecover method into JTS XATerminatorImple for WFTC inflow jca txn integration works

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2907?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2907: -------------------------------- Fix Version/s: 5.2.25.Final > Implement doRecover method into JTS XATerminatorImple for WFTC inflow jca txn integration works > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2907 > URL: https://issues.jboss.org/browse/JBTM-2907 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.6.1.Final, 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Blocker > Fix For: 5.2.25.Final, 5.next > > > When RAR calls {{XATerminator.recover(int)}} the call chain is not directed to Narayana implementation of XATerminator but it's passed to WFTC where {{ExtendedJBossXATerminator}} method {{doRecover}} is called. But the {{doRecover}} does not provide the expected recovery call - e.g. it does not accept flags ({{XAResource.TMSTARTRSCAN}}, {{XAResource.TMENDRSCAN}}) to drive the whole recovery process in case. > The biggest functionality trouble is for JTS where {{XATerminatorImple}} does not implement intentionally the {{doRecover}} function (https://github.com/jbosstm/narayana/blob/5.5.24.Final/ArjunaJTS/jtax/clas...). Thus RAR using call {{XATerminator.recover}} when JTS is under use does nothing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2907) Implement doRecover method into JTS XATerminatorImple for WFTC inflow jca txn integration works

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2907?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2907: -------------------------------- Fix Version/s: 5.next > Implement doRecover method into JTS XATerminatorImple for WFTC inflow jca txn integration works > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2907 > URL: https://issues.jboss.org/browse/JBTM-2907 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.6.1.Final, 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Blocker > Fix For: 5.next > > > When RAR calls {{XATerminator.recover(int)}} the call chain is not directed to Narayana implementation of XATerminator but it's passed to WFTC where {{ExtendedJBossXATerminator}} method {{doRecover}} is called. But the {{doRecover}} does not provide the expected recovery call - e.g. it does not accept flags ({{XAResource.TMSTARTRSCAN}}, {{XAResource.TMENDRSCAN}}) to drive the whole recovery process in case. > The biggest functionality trouble is for JTS where {{XATerminatorImple}} does not implement intentionally the {{doRecover}} function (https://github.com/jbosstm/narayana/blob/5.5.24.Final/ArjunaJTS/jtax/clas...). Thus RAR using call {{XATerminator.recover}} when JTS is under use does nothing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2905) JCAServerTransactionHeaderReader is placed under tests package which makes troubles for tooling

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2905?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2905: -------------------------------- Fix Version/s: 5.next > JCAServerTransactionHeaderReader is placed under tests package which makes troubles for tooling > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2905 > URL: https://issues.jboss.org/browse/JBTM-2905 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.6.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.next > > > The class {{JCAServerTransactionHeaderReader}} is placed under package {{com.hp.mwtests.ts.jta.jts.tools.}} which means is not available during runtime of tooling. As the header reader is used by {{com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser}} it brings situations where the record can't be loaded by tooling. The browser seems to be used by Expiry Scanner and that suffers by that fact. > The WFLY start sequence contains info of not possible to load the reader when the object store contains some unfinished jca subordinate transaction. > {code} > INFO [com.arjuna.ats.arjuna] (MSC service thread 1-4) ARJUNA012389: OSB: Error constructing record header reader: com.hp.mwtests.ts.jta.jts.tools.JCAServerTransactionHeaderReader from [Module "org.jboss.jts" from local module loader @6b419da (finder: local module finder @3b2da18f (roots: /home/ochaloup/Transactions/eap-tests-transactions/jbossts/target/jbossas-jbossts/modules,/home/ochaloup/jboss/jboss-eap-7.1.0.DR19/modules,/home/ochaloup/jboss/jboss-eap-7.1.0.DR19/modules/system/layers/base,/home/ochaloup/Transactions/eap-tests-transactions/jbossts/target/jbossas-jbossts/modules))] > {code} > The point is to move the jca reader under jts tooling package to be compiled and distributed in the {{jts}} jar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2905) JCAServerTransactionHeaderReader is placed under tests package which makes troubles for tooling

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2905?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2905: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > JCAServerTransactionHeaderReader is placed under tests package which makes troubles for tooling > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2905 > URL: https://issues.jboss.org/browse/JBTM-2905 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Tooling > Affects Versions: 5.6.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > The class {{JCAServerTransactionHeaderReader}} is placed under package {{com.hp.mwtests.ts.jta.jts.tools.}} which means is not available during runtime of tooling. As the header reader is used by {{com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser}} it brings situations where the record can't be loaded by tooling. The browser seems to be used by Expiry Scanner and that suffers by that fact. > The WFLY start sequence contains info of not possible to load the reader when the object store contains some unfinished jca subordinate transaction. > {code} > INFO [com.arjuna.ats.arjuna] (MSC service thread 1-4) ARJUNA012389: OSB: Error constructing record header reader: com.hp.mwtests.ts.jta.jts.tools.JCAServerTransactionHeaderReader from [Module "org.jboss.jts" from local module loader @6b419da (finder: local module finder @3b2da18f (roots: /home/ochaloup/Transactions/eap-tests-transactions/jbossts/target/jbossas-jbossts/modules,/home/ochaloup/jboss/jboss-eap-7.1.0.DR19/modules,/home/ochaloup/jboss/jboss-eap-7.1.0.DR19/modules/system/layers/base,/home/ochaloup/Transactions/eap-tests-transactions/jbossts/target/jbossas-jbossts/modules))] > {code} > The point is to move the jca reader under jts tooling package to be compiled and distributed in the {{jts}} jar. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2907) Implement doRecover method into JTS XATerminatorImple for WFTC inflow jca txn integration works

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2907?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ondra Chaloupka created pull request #1187 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Implement doRecover method into JTS XATerminatorImple for WFTC inflow jca txn integration works > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2907 > URL: https://issues.jboss.org/browse/JBTM-2907 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.6.1.Final, 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Blocker > > When RAR calls {{XATerminator.recover(int)}} the call chain is not directed to Narayana implementation of XATerminator but it's passed to WFTC where {{ExtendedJBossXATerminator}} method {{doRecover}} is called. But the {{doRecover}} does not provide the expected recovery call - e.g. it does not accept flags ({{XAResource.TMSTARTRSCAN}}, {{XAResource.TMENDRSCAN}}) to drive the whole recovery process in case. > The biggest functionality trouble is for JTS where {{XATerminatorImple}} does not implement intentionally the {{doRecover}} function (https://github.com/jbosstm/narayana/blob/5.5.24.Final/ArjunaJTS/jtax/clas...). Thus RAR using call {{XATerminator.recover}} when JTS is under use does nothing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2907) Implement doRecover method into JTS XATerminatorImple for WFTC inflow jca txn integration works

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2907?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-2907: --------------------------------------- per discussion with David and Tom the way of fixing JBEAP-11528 is to implement {{doRecover}} in JTS XATerminatorImple. The {{XATerminator.recover}} call from RAR is then provided to call {{doRecover(null,null}} which returns all subordinate in-doubt transactions which is expected. > Implement doRecover method into JTS XATerminatorImple for WFTC inflow jca txn integration works > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2907 > URL: https://issues.jboss.org/browse/JBTM-2907 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.6.1.Final, 5.5.24.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Blocker > > When RAR calls {{XATerminator.recover(int)}} the call chain is not directed to Narayana implementation of XATerminator but it's passed to WFTC where {{ExtendedJBossXATerminator}} method {{doRecover}} is called. But the {{doRecover}} does not provide the expected recovery call - e.g. it does not accept flags ({{XAResource.TMSTARTRSCAN}}, {{XAResource.TMENDRSCAN}}) to drive the whole recovery process in case. > The biggest functionality trouble is for JTS where {{XATerminatorImple}} does not implement intentionally the {{doRecover}} function (https://github.com/jbosstm/narayana/blob/5.5.24.Final/ArjunaJTS/jtax/clas...). Thus RAR using call {{XATerminator.recover}} when JTS is under use does nothing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2907) Implement doRecover method into JTS XATerminatorImple for WFTC inflow jca txn integration works

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2907?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka moved JBEAP-11580 to JBTM-2907: ----------------------------------------------- Project: JBoss Transaction Manager (was: JBoss Enterprise Application Platform) Key: JBTM-2907 (was: JBEAP-11580) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JTS (was: Transactions) Affects Version/s: 5.5.24.Final 5.6.1.Final (was: 7.1.0.ER1) > Implement doRecover method into JTS XATerminatorImple for WFTC inflow jca txn integration works > ----------------------------------------------------------------------------------------------- > > Key: JBTM-2907 > URL: https://issues.jboss.org/browse/JBTM-2907 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTS > Affects Versions: 5.5.24.Final, 5.6.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Blocker > > When RAR calls {{XATerminator.recover(int)}} the call chain is not directed to Narayana implementation of XATerminator but it's passed to WFTC where {{ExtendedJBossXATerminator}} method {{doRecover}} is called. But the {{doRecover}} does not provide the expected recovery call - e.g. it does not accept flags ({{XAResource.TMSTARTRSCAN}}, {{XAResource.TMENDRSCAN}}) to drive the whole recovery process in case. > The biggest functionality trouble is for JTS where {{XATerminatorImple}} does not implement intentionally the {{doRecover}} function (https://github.com/jbosstm/narayana/blob/5.5.24.Final/ArjunaJTS/jtax/clas...). Thus RAR using call {{XATerminator.recover}} when JTS is under use does nothing. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2906) It's not possible to combine start and end flags in call of XATerminator.recover

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2906?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2906: ------------------------------------- It might be nice and I see your point but: https://docs.oracle.com/javaee/7/api/javax/resource/spi/XATerminator.html... Described as "One of" However the XA spec does allow it: "TMENDRSCAN This flag indicates that xa_recover() should end the recovery scan after returning the XIDs. If this flag is used in conjunction with TMSTARTRSCAN, the single xa_recover() call starts and then ends a scan." So let's go with allowing it. > It's not possible to combine start and end flags in call of XATerminator.recover > --------------------------------------------------------------------------------- > > Key: JBTM-2906 > URL: https://issues.jboss.org/browse/JBTM-2906 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.6.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > Current implementation of {{XATerminator.recover}} (either for JTA or JTS) does not permit combining flags to use. > https://github.com/jbosstm/narayana/blob/5.6.1.Final/ArjunaJTA/jta/classe... > https://github.com/jbosstm/narayana/blob/5.6.1.Final/ArjunaJTS/jtax/class... > Flags are expected to be combined as their values are designed to use bitwise operators. Especially {{|}} is handy for starting and ending the recover scan in once. > Currently we need to call > {code} > XATerminator.recover(XAResource.TMSTARTRSCAN); > XATerminator.recover(XAResource.TMENDRSCAN); > {code} > Values are > {code} > XAResource.TMSTARTRSCAN : 16777216 : 1000000000000000000000000 > XAResource.TMENDRSCAN : 8388608 : 100000000000000000000000 > {code} > The way would be ability to call the {{recover}} like this > {code} > XATerminator.recover(XAResource.TMSTARTRSCAN | XAResource.TMENDRSCAN); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2906) It's not possible to combine start and end flags in call of XATerminator.recover

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2906?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-2906: ---------------------------------- Summary: It's not possible to combine start and end flags in call of XATerminator.recover (was: It's not psossible to combine start and end flags in call of XATerminator.recover ) > It's not possible to combine start and end flags in call of XATerminator.recover > --------------------------------------------------------------------------------- > > Key: JBTM-2906 > URL: https://issues.jboss.org/browse/JBTM-2906 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JCA > Affects Versions: 5.6.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > > Current implementation of {{XATerminator.recover}} (either for JTA or JTS) does not permit combining flags to use. > https://github.com/jbosstm/narayana/blob/5.6.1.Final/ArjunaJTA/jta/classe... > https://github.com/jbosstm/narayana/blob/5.6.1.Final/ArjunaJTS/jtax/class... > Flags are expected to be combined as their values are designed to use bitwise operators. Especially {{|}} is handy for starting and ending the recover scan in once. > Currently we need to call > {code} > XATerminator.recover(XAResource.TMSTARTRSCAN); > XATerminator.recover(XAResource.TMENDRSCAN); > {code} > Values are > {code} > XAResource.TMSTARTRSCAN : 16777216 : 1000000000000000000000000 > XAResource.TMENDRSCAN : 8388608 : 100000000000000000000000 > {code} > The way would be ability to call the {{recover}} like this > {code} > XATerminator.recover(XAResource.TMSTARTRSCAN | XAResource.TMENDRSCAN); > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 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 June 2017