April 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2161) Allow the list of jndi names to contact in the CMR recovery module to be refreshed when a new CMR resource is added

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2161?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2161: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/646 > Allow the list of jndi names to contact in the CMR recovery module to be refreshed when a new CMR resource is added > ------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2161 > URL: https://issues.jboss.org/browse/JBTM-2161 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Resource Manager > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 4.17.20, 5.0.2 > > > Currently the list is fixed at startup time as it is stored in a list, as there is no real performance impact of checking the list once every 120 seconds and it will allow resources to be more dynamically added (at least for recovery). > It would assist with: https://bugzilla.redhat.com/show_bug.cgi?id=1091308 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2160) ActivityHierarchy comparison fails

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2160?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-2160: -------------------------------- Description: To reproduce: {code} CoordinatorManager cm1 = CoordinatorManagerFactory.coordinatorManager(); CoordinatorManager cm2 = CoordinatorManagerFactory.coordinatorManager(); cm1.begin("Sagas11HLS"); ActivityHierarchy hierarchy1 = cm1.suspend(); cm2.begin("Sagas11HLS"); ActivityHierarchy hierarchy2 = cm2.suspend(); Assert.assertFalse(hierarchy1.equals(hierarchy2)); {code} The assertion fails. It is caused by a broken isEqual method and also an omitted cast. See the fix for details. was: To reproduce: To reproduce: {code} CoordinatorManager cm1 = CoordinatorManagerFactory.coordinatorManager(); CoordinatorManager cm2 = CoordinatorManagerFactory.coordinatorManager(); cm1.begin("Sagas11HLS"); ActivityHierarchy hierarchy1 = cm1.suspend(); cm2.begin("Sagas11HLS"); ActivityHierarchy hierarchy2 = cm2.suspend(); Assert.assertFalse(hierarchy1.equals(hierarchy2)); {code} The assertion fails. It is caused by a broken isEqual method and also a omitted cast. See the fix for details. > ActivityHierarchy comparison fails > ---------------------------------- > > Key: JBTM-2160 > URL: https://issues.jboss.org/browse/JBTM-2160 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.2 > > > To reproduce: > {code} > CoordinatorManager cm1 = CoordinatorManagerFactory.coordinatorManager(); > CoordinatorManager cm2 = CoordinatorManagerFactory.coordinatorManager(); > cm1.begin("Sagas11HLS"); > ActivityHierarchy hierarchy1 = cm1.suspend(); > cm2.begin("Sagas11HLS"); > ActivityHierarchy hierarchy2 = cm2.suspend(); > Assert.assertFalse(hierarchy1.equals(hierarchy2)); > {code} > The assertion fails. It is caused by a broken isEqual method and also an omitted cast. See the fix for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2160) ActivityHierarchy comparison fails

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2160?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-2160: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ActivityHierarchy comparison fails > ---------------------------------- > > Key: JBTM-2160 > URL: https://issues.jboss.org/browse/JBTM-2160 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.2 > > > To reproduce: > {code} > CoordinatorManager cm1 = CoordinatorManagerFactory.coordinatorManager(); > CoordinatorManager cm2 = CoordinatorManagerFactory.coordinatorManager(); > cm1.begin("Sagas11HLS"); > ActivityHierarchy hierarchy1 = cm1.suspend(); > cm2.begin("Sagas11HLS"); > ActivityHierarchy hierarchy2 = cm2.suspend(); > Assert.assertFalse(hierarchy1.equals(hierarchy2)); > {code} > The assertion fails. It is caused by a broken isEqual method and also an omitted cast. See the fix for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2161) Allow the list of jndi names to contact in the CMR recovery module to be refreshed when a new CMR resource is added

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-2161: ----------------------------------- Summary: Allow the list of jndi names to contact in the CMR recovery module to be refreshed when a new CMR resource is added Key: JBTM-2161 URL: https://issues.jboss.org/browse/JBTM-2161 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Resource Manager Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 4.17.20, 5.0.2 Currently the list is fixed at startup time as it is stored in a list, as there is no real performance impact of checking the list once every 120 seconds and it will allow resources to be more dynamically added (at least for recovery). It would assist with: https://bugzilla.redhat.com/show_bug.cgi?id=1091308 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2135) QA suite failure: CrashRecovery08_Test22

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2135?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-2135. ------------------------------------ Resolution: Won't Fix It is obvious from the logs what the issue. > QA suite failure: CrashRecovery08_Test22 > ---------------------------------------- > > Key: JBTM-2135 > URL: https://issues.jboss.org/browse/JBTM-2135 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.2 > > Attachments: narayana-jdbcobjectstore_67_mysql_CrashRecovery08_Test22.zip > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/6... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2160) ActivityHierarchy comparison fails

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2160?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-2160: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/645 > ActivityHierarchy comparison fails > ---------------------------------- > > Key: JBTM-2160 > URL: https://issues.jboss.org/browse/JBTM-2160 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.2 > > > To reproduce: > To reproduce: > {code} > CoordinatorManager cm1 = CoordinatorManagerFactory.coordinatorManager(); > CoordinatorManager cm2 = CoordinatorManagerFactory.coordinatorManager(); > cm1.begin("Sagas11HLS"); > ActivityHierarchy hierarchy1 = cm1.suspend(); > cm2.begin("Sagas11HLS"); > ActivityHierarchy hierarchy2 = cm2.suspend(); > Assert.assertFalse(hierarchy1.equals(hierarchy2)); > {code} > The assertion fails. It is caused by a broken isEqual method and also a omitted cast. See the fix for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2160) ActivityHierarchy comparison fails

by Paul Robinson (JIRA)

Paul Robinson created JBTM-2160: ----------------------------------- Summary: ActivityHierarchy comparison fails Key: JBTM-2160 URL: https://issues.jboss.org/browse/JBTM-2160 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.2 To reproduce: To reproduce: {code} CoordinatorManager cm1 = CoordinatorManagerFactory.coordinatorManager(); CoordinatorManager cm2 = CoordinatorManagerFactory.coordinatorManager(); cm1.begin("Sagas11HLS"); ActivityHierarchy hierarchy1 = cm1.suspend(); cm2.begin("Sagas11HLS"); ActivityHierarchy hierarchy2 = cm2.suspend(); Assert.assertFalse(hierarchy1.equals(hierarchy2)); {code} The assertion fails. It is caused by a broken isEqual method and also a omitted cast. See the fix for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2135) QA suite failure: CrashRecovery08_Test22

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2135?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-2135: ------------------------------------- AIUI this occured once so probably not a big deal, we just need a way to be able to identify it quickly in future I suppose? Was it really obvious from the logs what the issue was and if not maybe we could look at some addtional info in our stack trace? > QA suite failure: CrashRecovery08_Test22 > ---------------------------------------- > > Key: JBTM-2135 > URL: https://issues.jboss.org/browse/JBTM-2135 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.2 > > Attachments: narayana-jdbcobjectstore_67_mysql_CrashRecovery08_Test22.zip > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/6... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2135) QA suite failure: CrashRecovery08_Test22

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2135?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2135: ---------------------------------------- The failure is caused by a MySql deadlock when client0 initialises the OTSManager (com.mysql.jdbc.exceptions.jdbc4.MySQLTransactionRollbackException: Deadlock found when trying to get lock; try restarting transaction) whilst writing a "FactoryContactItem" record to the store. It isn't clear from the logs which other process and locks are involved. The advice in the MySQL docs is: bq. Always be prepared to re-issue a transaction if it fails due to deadlock. Deadlocks are not dangerous. Just try again. Do we think it is worthwhile changing retrying failed JDBCStore.write_committed operations > QA suite failure: CrashRecovery08_Test22 > ---------------------------------------- > > Key: JBTM-2135 > URL: https://issues.jboss.org/browse/JBTM-2135 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.2 > > Attachments: narayana-jdbcobjectstore_67_mysql_CrashRecovery08_Test22.zip > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/6... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2154) QA suite failure with db2 in jobs 71 and 72

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2154?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2154: -------------------------------- Priority: Critical (was: Major) > QA suite failure with db2 in jobs 71 and 72 > ------------------------------------------- > > Key: JBTM-2154 > URL: https://issues.jboss.org/browse/JBTM-2154 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.0.2 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-jdbcobjectstore/7... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 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 April 2014