May 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1712) perf problem in FileSystemStore.openAndLock

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1712?page=com.atlassian.jira.plugin.... ] Mark Little closed JBTM-1712. ----------------------------- > perf problem in FileSystemStore.openAndLock > ------------------------------------------- > > Key: JBTM-1712 > URL: https://issues.jboss.org/browse/JBTM-1712 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.16.4, 5.0.0.M2 > Reporter: Jonathan Halliday > Assignee: Mark Little > Fix For: 5.0.0.M3 > > > if(!file.exits()) > { > if(createHierarchy(file)) > incorrectly calls the expensive (because synchronized) createHierarchy method in the common case where the file does not exist (because it's a uniq named new tx record) but the directory hierarchy does (because it's the create-once hashed dir tree). This causes excessive contention on the FileSystemStore instance object monitor lock. Should probably be something more like > if(!file.getParent().exists()) > { > if(createHierarchy(file)) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1712) perf problem in FileSystemStore.openAndLock

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1712?page=com.atlassian.jira.plugin.... ] Mark Little updated JBTM-1712: ------------------------------ Affects Version/s: 5.0.0.M2 > perf problem in FileSystemStore.openAndLock > ------------------------------------------- > > Key: JBTM-1712 > URL: https://issues.jboss.org/browse/JBTM-1712 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.16.4, 5.0.0.M2 > Reporter: Jonathan Halliday > Assignee: Mark Little > > if(!file.exits()) > { > if(createHierarchy(file)) > incorrectly calls the expensive (because synchronized) createHierarchy method in the common case where the file does not exist (because it's a uniq named new tx record) but the directory hierarchy does (because it's the create-once hashed dir tree). This causes excessive contention on the FileSystemStore instance object monitor lock. Should probably be something more like > if(!file.getParent().exists()) > { > if(createHierarchy(file)) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1712) perf problem in FileSystemStore.openAndLock

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1712?page=com.atlassian.jira.plugin.... ] Mark Little updated JBTM-1712: ------------------------------ Fix Version/s: 5.0.0.M3 > perf problem in FileSystemStore.openAndLock > ------------------------------------------- > > Key: JBTM-1712 > URL: https://issues.jboss.org/browse/JBTM-1712 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.16.4, 5.0.0.M2 > Reporter: Jonathan Halliday > Assignee: Mark Little > Fix For: 5.0.0.M3 > > > if(!file.exits()) > { > if(createHierarchy(file)) > incorrectly calls the expensive (because synchronized) createHierarchy method in the common case where the file does not exist (because it's a uniq named new tx record) but the directory hierarchy does (because it's the create-once hashed dir tree). This causes excessive contention on the FileSystemStore instance object monitor lock. Should probably be something more like > if(!file.getParent().exists()) > { > if(createHierarchy(file)) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1563) TestTransactions::test_recovery (F) line: 520 /home/hudson/workspace/blacktie-linux64/tx/src/test/cpp/TestTransactions.cxx

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1563?page=com.atlassian.jira.plugin.... ] Mark Little commented on JBTM-1563: ----------------------------------- Thanks. Maybe update the Description part of the JIRA? > TestTransactions::test_recovery (F) line: 520 /home/hudson/workspace/blacktie-linux64/tx/src/test/cpp/TestTransactions.cxx > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1563 > URL: https://issues.jboss.org/browse/JBTM-1563 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Testing > Affects Versions: 5.0.0.M1 > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.Final > > > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64-el5/1423/... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1712) perf problem in FileSystemStore.openAndLock

by Mark Little (JIRA)

[ https://issues.jboss.org/browse/JBTM-1712?page=com.atlassian.jira.plugin.... ] Work on JBTM-1712 started by Mark Little. > perf problem in FileSystemStore.openAndLock > ------------------------------------------- > > Key: JBTM-1712 > URL: https://issues.jboss.org/browse/JBTM-1712 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Transaction Core > Affects Versions: 4.16.4 > Reporter: Jonathan Halliday > Assignee: Mark Little > > if(!file.exits()) > { > if(createHierarchy(file)) > incorrectly calls the expensive (because synchronized) createHierarchy method in the common case where the file does not exist (because it's a uniq named new tx record) but the directory hierarchy does (because it's the create-once hashed dir tree). This causes excessive contention on the FileSystemStore instance object monitor lock. Should probably be something more like > if(!file.getParent().exists()) > { > if(createHierarchy(file)) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1676) Integrate Compensations API with WS-BA

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1676?focusedWorklogId=12429205&page=... ] Paul Robinson logged work on JBTM-1676: --------------------------------------- Author: Paul Robinson Created on: 25/May/13 5:31 AM Start Date: 25/May/13 5:31 AM Worklog Time Spent: 1 day Issue Time Tracking ------------------- Remaining Estimate: 0 minutes (was: 2 days) Time Spent: 1 day Worklog Id: (was: 12429205) > Integrate Compensations API with WS-BA > -------------------------------------- > > Key: JBTM-1676 > URL: https://issues.jboss.org/browse/JBTM-1676 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M3 > > Original Estimate: 2 days > Time Spent: 1 day > Remaining Estimate: 0 minutes > > The current implementation of the Compensations API is using WS-BA under the covers, so it should be relatively straight forward to use WS-BA to distribute the transaction. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1676) Integrate Compensations API with WS-BA

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1676?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1676. --------------------------------- Resolution: Done > Integrate Compensations API with WS-BA > -------------------------------------- > > Key: JBTM-1676 > URL: https://issues.jboss.org/browse/JBTM-1676 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M3 > > Original Estimate: 2 days > Time Spent: 1 day > Remaining Estimate: 0 minutes > > The current implementation of the Compensations API is using WS-BA under the covers, so it should be relatively straight forward to use WS-BA to distribute the transaction. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1710) CDI @Inject doesn't work in CompensationHandler et al

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1710?page=com.atlassian.jira.plugin.... ] Paul Robinson resolved JBTM-1710. --------------------------------- Resolution: Done > CDI @Inject doesn't work in CompensationHandler et al > ----------------------------------------------------- > > Key: JBTM-1710 > URL: https://issues.jboss.org/browse/JBTM-1710 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M3 > > > org.jboss.narayana.compensations.impl.Participant uses class.newInstance to create the handler instance. This means that Weld does not handle the @Inject annotation. > Creating the instance via the BeanManager solves this problem. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1685) QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2#Test28

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1685?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1685: ----------------------------------- Fix Version/s: 5.0.0.M4 (was: 5.0.0.M3) > QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery02_2#Test28 > ----------------------------------------------------------------------------------------- > > Key: JBTM-1685 > URL: https://issues.jboss.org/browse/JBTM-1685 > 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.0.M4 > > Attachments: CrashRecovery02_2_Test28.zip > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/99/cons... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1686) QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1686?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1686: ----------------------------------- Fix Version/s: 5.0.0.M4 (was: 5.0.0.M3) > QA suite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2 > ---------------------------------------------------------------------------------- > > Key: JBTM-1686 > URL: https://issues.jboss.org/browse/JBTM-1686 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.0.M4 > > Attachments: crashrecovery05_2.zip > > > http://172.17.131.2/job/jbossts-EAP61-jdbcobjectstore/DB_TYPE=postgres,jd... -- 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, 11 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 May 2013