July 2016 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2709) ObjectStoreBrowser cannot cope with JDBC store on Windows

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2709: ----------------------------------- Summary: ObjectStoreBrowser cannot cope with JDBC store on Windows Key: JBTM-2709 URL: https://issues.jboss.org/browse/JBTM-2709 Project: JBoss Transaction Manager Issue Type: Task Reporter: Tom Jenkinson While testing backport of JBTM-2614 I came across the ObjStoreBrowser test. This was failing on Windows. On looking into it I saw it was because the Browser map swaps the "/" in the type name to the system file separator path. This is likely because of the file system store. I have a fix that puts the entry in both ways but it will likely need some more work so providing as an example. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2709) ObjectStoreBrowser cannot cope with JDBC store on Windows

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2709?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2709: ----------------------------------- Assignee: Michael Musgrove > ObjectStoreBrowser cannot cope with JDBC store on Windows > --------------------------------------------------------- > > Key: JBTM-2709 > URL: https://issues.jboss.org/browse/JBTM-2709 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > While testing backport of JBTM-2614 I came across the ObjStoreBrowser test. This was failing on Windows. On looking into it I saw it was because the Browser map swaps the "/" in the type name to the system file separator path. This is likely because of the file system store. I have a fix that puts the entry in both ways but it will likely need some more work so providing as an example. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2708) Test does not close FileInputStream

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2708: ----------------------------------- Summary: Test does not close FileInputStream Key: JBTM-2708 URL: https://issues.jboss.org/browse/JBTM-2708 Project: JBoss Transaction Manager Issue Type: Task Components: Testing Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next {code} public XARRTestResource(String xarrHelper, File file) throws IOException { this.xarrHelper = xarrHelper; this.file = file; DataInputStream fis = new DataInputStream(new FileInputStream(file)); final int formatId = fis.readInt(); final int gtrid_length = fis.readInt(); final byte[] gtrid = new byte[gtrid_length]; fis.read(gtrid, 0, gtrid_length); final int bqual_length = fis.readInt(); final byte[] bqual = new byte[bqual_length]; fis.read(bqual, 0, bqual_length); xids.put(file, new Xid() { @Override public byte[] getGlobalTransactionId() { return gtrid; } @Override public int getFormatId() { return formatId; } @Override public byte[] getBranchQualifier() { return bqual; } }); fis.close(); } {code} Spotted while working on JBTM-2614 backport -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2701) XAR should be scanned more frequently for prepared transactions

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2701?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2701: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Unresolved > XAR should be scanned more frequently for prepared transactions > --------------------------------------------------------------- > > Key: JBTM-2701 > URL: https://issues.jboss.org/browse/JBTM-2701 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 4.17.33 > Environment: JBoss EA P6.4.8 > Reporter: Tom Ross > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > The JCA getNewXAResource() call can only bring forward the scanning of XAResources once per recovery pass (i.e. once every two minutes per default). > The following signature can be observed in the log file: > {noformat} > 2016-06-28 12:18:33,068 TRACE [com.arjuna.ats.jta] (EJB default - 98) XAResourceRecord.topLevelCommit for XAResourceRecord < resource:null, txid:< formatId=131077, gtrid_length=40, bqual_length=48, tx_uid=0:ffff0af7f615:19718dac:576e895c:d7da9, node_name=svc_1_cmserv, branch_uid=0:ffff0af7f663:ba85fe7:57714e42:7058f2, subordinatenodename=svc_2_mscmce, eis_name=java:/eis/custom-ra >, heuristic: TwoPhaseOutcome.FINISH_OK, product: com/ecim/1.0, jndiName: java:/eis/custom-ra com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@64fa6d0e >, record id=0:ffff0af7f663:ba85fe7:57714e42:7058f3 > 2016-06-28 12:18:33,068 WARN [com.arjuna.ats.jta] (EJB default - 98) ARJUNA016038: No XAResource to recover < formatId=131077, gtrid_length=40, bqual_length=48, tx_uid=0:ffff0af7f615:19718dac:576e895c:d7da9, node_name=svc_1_cmserv, branch_uid=0:ffff0af7f663:ba85fe7:57714e42:7058f2, subordinatenodename=svc_2_mscmce, eis_name=java:/eis/custom-ra > > 2016-06-28 12:18:33,069 TRACE [com.arjuna.ats.arjuna] (EJB default - 98) BasicAction.doCommit for 0:ffff0af7f663:ba85fe7:57714e42:705303 received TwoPhaseOutcome.FINISH_ERROR from class com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord > 2016-06-28 12:18:33,069 TRACE [com.arjuna.ats.arjuna] (EJB default - 98) RecordList::insert(RecordList: empty) : appending /StateManager/AbstractRecord/XAResourceRecord for 0:ffff0af7f663:ba85fe7:57714e42:7058f3 > {noformat} > It would be useful to allow the getNewXAResource() call to re-scan XAR in case it is called in between recovery scans multiple times. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2701) XAR should be scanned more frequently for prepared transactions

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2701?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reopened JBTM-2701: --------------------------------- > XAR should be scanned more frequently for prepared transactions > --------------------------------------------------------------- > > Key: JBTM-2701 > URL: https://issues.jboss.org/browse/JBTM-2701 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 4.17.33 > Environment: JBoss EA P6.4.8 > Reporter: Tom Ross > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > The JCA getNewXAResource() call can only bring forward the scanning of XAResources once per recovery pass (i.e. once every two minutes per default). > The following signature can be observed in the log file: > {noformat} > 2016-06-28 12:18:33,068 TRACE [com.arjuna.ats.jta] (EJB default - 98) XAResourceRecord.topLevelCommit for XAResourceRecord < resource:null, txid:< formatId=131077, gtrid_length=40, bqual_length=48, tx_uid=0:ffff0af7f615:19718dac:576e895c:d7da9, node_name=svc_1_cmserv, branch_uid=0:ffff0af7f663:ba85fe7:57714e42:7058f2, subordinatenodename=svc_2_mscmce, eis_name=java:/eis/custom-ra >, heuristic: TwoPhaseOutcome.FINISH_OK, product: com/ecim/1.0, jndiName: java:/eis/custom-ra com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@64fa6d0e >, record id=0:ffff0af7f663:ba85fe7:57714e42:7058f3 > 2016-06-28 12:18:33,068 WARN [com.arjuna.ats.jta] (EJB default - 98) ARJUNA016038: No XAResource to recover < formatId=131077, gtrid_length=40, bqual_length=48, tx_uid=0:ffff0af7f615:19718dac:576e895c:d7da9, node_name=svc_1_cmserv, branch_uid=0:ffff0af7f663:ba85fe7:57714e42:7058f2, subordinatenodename=svc_2_mscmce, eis_name=java:/eis/custom-ra > > 2016-06-28 12:18:33,069 TRACE [com.arjuna.ats.arjuna] (EJB default - 98) BasicAction.doCommit for 0:ffff0af7f663:ba85fe7:57714e42:705303 received TwoPhaseOutcome.FINISH_ERROR from class com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord > 2016-06-28 12:18:33,069 TRACE [com.arjuna.ats.arjuna] (EJB default - 98) RecordList::insert(RecordList: empty) : appending /StateManager/AbstractRecord/XAResourceRecord for 0:ffff0af7f663:ba85fe7:57714e42:7058f3 > {noformat} > It would be useful to allow the getNewXAResource() call to re-scan XAR in case it is called in between recovery scans multiple times. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2701) XAR should be scanned more frequently for prepared transactions

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2701?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2701: -------------------------------- Priority: Minor (was: Major) > XAR should be scanned more frequently for prepared transactions > --------------------------------------------------------------- > > Key: JBTM-2701 > URL: https://issues.jboss.org/browse/JBTM-2701 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 4.17.33 > Environment: JBoss EA P6.4.8 > Reporter: Tom Ross > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > The JCA getNewXAResource() call can only bring forward the scanning of XAResources once per recovery pass (i.e. once every two minutes per default). > The following signature can be observed in the log file: > {noformat} > 2016-06-28 12:18:33,068 TRACE [com.arjuna.ats.jta] (EJB default - 98) XAResourceRecord.topLevelCommit for XAResourceRecord < resource:null, txid:< formatId=131077, gtrid_length=40, bqual_length=48, tx_uid=0:ffff0af7f615:19718dac:576e895c:d7da9, node_name=svc_1_cmserv, branch_uid=0:ffff0af7f663:ba85fe7:57714e42:7058f2, subordinatenodename=svc_2_mscmce, eis_name=java:/eis/custom-ra >, heuristic: TwoPhaseOutcome.FINISH_OK, product: com/ecim/1.0, jndiName: java:/eis/custom-ra com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@64fa6d0e >, record id=0:ffff0af7f663:ba85fe7:57714e42:7058f3 > 2016-06-28 12:18:33,068 WARN [com.arjuna.ats.jta] (EJB default - 98) ARJUNA016038: No XAResource to recover < formatId=131077, gtrid_length=40, bqual_length=48, tx_uid=0:ffff0af7f615:19718dac:576e895c:d7da9, node_name=svc_1_cmserv, branch_uid=0:ffff0af7f663:ba85fe7:57714e42:7058f2, subordinatenodename=svc_2_mscmce, eis_name=java:/eis/custom-ra > > 2016-06-28 12:18:33,069 TRACE [com.arjuna.ats.arjuna] (EJB default - 98) BasicAction.doCommit for 0:ffff0af7f663:ba85fe7:57714e42:705303 received TwoPhaseOutcome.FINISH_ERROR from class com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord > 2016-06-28 12:18:33,069 TRACE [com.arjuna.ats.arjuna] (EJB default - 98) RecordList::insert(RecordList: empty) : appending /StateManager/AbstractRecord/XAResourceRecord for 0:ffff0af7f663:ba85fe7:57714e42:7058f3 > {noformat} > It would be useful to allow the getNewXAResource() call to re-scan XAR in case it is called in between recovery scans multiple times. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2701) XAR should be scanned more frequently for prepared transactions

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2701?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2701: ----------------------------------- Assignee: Michael Musgrove (was: Amos Feng) > XAR should be scanned more frequently for prepared transactions > --------------------------------------------------------------- > > Key: JBTM-2701 > URL: https://issues.jboss.org/browse/JBTM-2701 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 4.17.33 > Environment: JBoss EA P6.4.8 > Reporter: Tom Ross > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > > The JCA getNewXAResource() call can only bring forward the scanning of XAResources once per recovery pass (i.e. once every two minutes per default). > The following signature can be observed in the log file: > {noformat} > 2016-06-28 12:18:33,068 TRACE [com.arjuna.ats.jta] (EJB default - 98) XAResourceRecord.topLevelCommit for XAResourceRecord < resource:null, txid:< formatId=131077, gtrid_length=40, bqual_length=48, tx_uid=0:ffff0af7f615:19718dac:576e895c:d7da9, node_name=svc_1_cmserv, branch_uid=0:ffff0af7f663:ba85fe7:57714e42:7058f2, subordinatenodename=svc_2_mscmce, eis_name=java:/eis/custom-ra >, heuristic: TwoPhaseOutcome.FINISH_OK, product: com/ecim/1.0, jndiName: java:/eis/custom-ra com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord@64fa6d0e >, record id=0:ffff0af7f663:ba85fe7:57714e42:7058f3 > 2016-06-28 12:18:33,068 WARN [com.arjuna.ats.jta] (EJB default - 98) ARJUNA016038: No XAResource to recover < formatId=131077, gtrid_length=40, bqual_length=48, tx_uid=0:ffff0af7f615:19718dac:576e895c:d7da9, node_name=svc_1_cmserv, branch_uid=0:ffff0af7f663:ba85fe7:57714e42:7058f2, subordinatenodename=svc_2_mscmce, eis_name=java:/eis/custom-ra > > 2016-06-28 12:18:33,069 TRACE [com.arjuna.ats.arjuna] (EJB default - 98) BasicAction.doCommit for 0:ffff0af7f663:ba85fe7:57714e42:705303 received TwoPhaseOutcome.FINISH_ERROR from class com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord > 2016-06-28 12:18:33,069 TRACE [com.arjuna.ats.arjuna] (EJB default - 98) RecordList::insert(RecordList: empty) : appending /StateManager/AbstractRecord/XAResourceRecord for 0:ffff0af7f663:ba85fe7:57714e42:7058f3 > {noformat} > It would be useful to allow the getNewXAResource() call to re-scan XAR in case it is called in between recovery scans multiple times. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2693) jca-and-hibernate quickstart CI failure

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2693?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2693: ---------------------------------- Fix Version/s: 5.next > jca-and-hibernate quickstart CI failure > --------------------------------------- > > Key: JBTM-2693 > URL: https://issues.jboss.org/browse/JBTM-2693 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.next > > > The quickstart fails with a hibernate constraint violation: > CI output: http://172.17.130.4:8083/job/narayana-quickstarts-ipv6/28 > Output: > {quote} > 2016-06-18 07:36:23,944 [main] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - Unique index or primary key violation: "UK_6M4FUHXJ4CKIXI1VSB8OSII7R_INDEX_5 ON PUBLIC.CUSTOMER(NAME)"; SQL statement: > insert into Customer (name, id) values (?, ?) [23505-171] > 2016-06-18 07:36:23,947 [main] WARN com.arjuna.ats.arjuna - ARJUNA012125: TwoPhaseCoordinator.beforeCompletion - failed for SynchronizationImple< -180000000000000:22cf30fffe66b53b:d118:5764ebe6:2a, org.hibernate.engine.transaction.synchronization.internal.RegisteredSynchronization@1b0a7baf > > javax.persistence.PersistenceException: org.hibernate.exception.ConstraintViolationException: could not execute statement > 2016-06-18 07:36:23,944 [main] ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper - Unique index or primary key violation: "UK_6M4FUHXJ4CKIXI1VSB8OSII7R_INDEX_5 ON PUBLIC.CUSTOMER(NAME)"; SQL statement: > insert into Customer (name, id) values (?, ?) [23505-171] > 2016-06-18 07:36:23,947 [main] WARN com.arjuna.ats.arjuna - ARJUNA012125: TwoPhaseCoordinator.beforeCompletion - failed for SynchronizationImple< -180000000000000:22cf30fffe66b53b:d118:5764ebe6:2a, org.hibernate.engine.transaction.synchronization.internal.RegisteredSynchronization@1b0a7baf > > javax.persistence.PersistenceException: org.hibernate.exception.ConstraintViolationException: could not execute statement > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2707) Update README to reflect accurately which JDK versions we support

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2707?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-2707. ------------------------------------ Resolution: Done The maven enforcer plugin enforces JDK version 1.8 and I have updated the README.md to reflect that. > Update README to reflect accurately which JDK versions we support > ----------------------------------------------------------------- > > Key: JBTM-2707 > URL: https://issues.jboss.org/browse/JBTM-2707 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > We are using Java 1.8 features and the top level README needs to reflect tha. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2707) Update README to reflect accurately which JDK versions we support

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2707: -------------------------------------- Summary: Update README to reflect accurately which JDK versions we support Key: JBTM-2707 URL: https://issues.jboss.org/browse/JBTM-2707 Project: JBoss Transaction Manager Issue Type: Bug Components: Documentation Affects Versions: 5.3.3.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next We are using Java 1.8 features and the top level README needs to reflect tha. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2016