July 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1851) Update Wildfly version to 8.0.0.Alpha4-SNAPSHOT

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1851?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-1851: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/382 > Update Wildfly version to 8.0.0.Alpha4-SNAPSHOT > ----------------------------------------------- > > Key: JBTM-1851 > URL: https://issues.jboss.org/browse/JBTM-1851 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Configuration > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.0.0.M4 > > -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1851) Update Wildfly version to 8.0.0.Alpha4-SNAPSHOT

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-1851: ------------------------------------- Summary: Update Wildfly version to 8.0.0.Alpha4-SNAPSHOT Key: JBTM-1851 URL: https://issues.jboss.org/browse/JBTM-1851 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.0.0.M4 -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1850) org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.6.Final-SNAPSHOT artefact is missing

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1850?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1850. --------------------------------- Resolution: Done Sorry, I was between releases and should have deleted this build as I "resolved" it at the time. Thanks for the Jira to remind me though :) > org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.6.Final-SNAPSHOT artefact is missing > ----------------------------------------------------------------------------------- > > Key: JBTM-1850 > URL: https://issues.jboss.org/browse/JBTM-1850 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTS > Affects Versions: 4.17.6 > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Minor > > http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-EAP61/1809/console... > {code} > [INFO] ------------------------------------------------------------------------ > [INFO] Building JBoss Application Server: JacORB Subsystem 7.2.0.Final > [INFO] ------------------------------------------------------------------------ > Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jbossts... > Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jbossts... > [WARNING] The POM for org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.6.Final-SNAPSHOT is missing, no dependency information available > Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jbossts... > {code} > {code} > [ERROR] Failed to execute goal on project jboss-as-jacorb: Could not resolve dependencies for project org.jboss.as:jboss-as-jacorb:jar:7.2.0.Final: Could not find artifact org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.6.Final-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExce... > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn <goals> -rf :jboss-as-jacorb > {code} -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1850) org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.6.Final-SNAPSHOT artefact is missing

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-1850: ------------------------------------- Summary: org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.6.Final-SNAPSHOT artefact is missing Key: JBTM-1850 URL: https://issues.jboss.org/browse/JBTM-1850 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Affects Versions: 4.17.6 Reporter: Gytis Trikleris Assignee: Tom Jenkinson Priority: Minor http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-EAP61/1809/console... {code} [INFO] ------------------------------------------------------------------------ [INFO] Building JBoss Application Server: JacORB Subsystem 7.2.0.Final [INFO] ------------------------------------------------------------------------ Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jbossts... Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jbossts... [WARNING] The POM for org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.6.Final-SNAPSHOT is missing, no dependency information available Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jbossts... {code} {code} [ERROR] Failed to execute goal on project jboss-as-jacorb: Could not resolve dependencies for project org.jboss.as:jboss-as-jacorb:jar:7.2.0.Final: Could not find artifact org.jboss.jbossts.jts:jbossjts-jacorb:jar:4.17.6.Final-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExce... [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :jboss-as-jacorb {code} -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1849) Blacktie quickstart timed out

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-1849: ------------------------------------- Summary: Blacktie quickstart timed out Key: JBTM-1849 URL: https://issues.jboss.org/browse/JBTM-1849 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: BlackTie, Demonstrator Reporter: Gytis Trikleris Assignee: Amos Feng Priority: Minor Fix For: 5.0.0.M4 http://172.17.131.2/view/Narayana+BlackTie/job/narayana-quickstarts-windo... -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1786) Change to TMFAIL for an ABORT on a non-prepared TX

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1786?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1786: -------------------------------- Fix Version/s: 4.17.7 > Change to TMFAIL for an ABORT on a non-prepared TX > -------------------------------------------------- > > Key: JBTM-1786 > URL: https://issues.jboss.org/browse/JBTM-1786 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA, JTS > Affects Versions: 4.16.4 > Reporter: Johnathon Lee > Assignee: Johnathon Lee > Fix For: 4.17.7, 5.0.0.M4 > > > An ABORT on a non-prepared TX should be calling end with TMFAIL. > It's more efficient in that the RM can return an RB* code immediately and short circuit the rollback internally if it likes. More importantly though the RM is less likely to object that it's still running tx activity on another thread and the concurrent TMSUCCESS therefore makes no sense to it. > Also the XAResourceRecord.topLevelAbort code should immediately continue on to calling rollback on the resource despite the failed end(). -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1786) Change to TMFAIL for an ABORT on a non-prepared TX

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1786?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1786: -------------------------------- Fix Version/s: 5.0.0.M4 > Change to TMFAIL for an ABORT on a non-prepared TX > -------------------------------------------------- > > Key: JBTM-1786 > URL: https://issues.jboss.org/browse/JBTM-1786 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA, JTS > Affects Versions: 4.16.4 > Reporter: Johnathon Lee > Assignee: Johnathon Lee > Fix For: 5.0.0.M4 > > > An ABORT on a non-prepared TX should be calling end with TMFAIL. > It's more efficient in that the RM can return an RB* code immediately and short circuit the rollback internally if it likes. More importantly though the RM is less likely to object that it's still running tx activity on another thread and the concurrent TMSUCCESS therefore makes no sense to it. > Also the XAResourceRecord.topLevelAbort code should immediately continue on to calling rollback on the resource despite the failed end(). -- 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

12 years, 8 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-1712?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-1712: ----------------------------------------------- tom.jenkinson(a)redhat.com changed the Status of [bug 968125|https://bugzilla.redhat.com/show_bug.cgi?id=968125] from ASSIGNED to POST > 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: 4.17.6, 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

12 years, 8 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-1712?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTM-1712: ----------------------------------------------- tom.jenkinson(a)redhat.com made a comment on [bug 968125|https://bugzilla.redhat.com/show_bug.cgi?id=968125] PR over here: https://github.com/jbossas/jboss-eap/pull/245 > 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: 4.17.6, 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1786) Change to TMFAIL for an ABORT on a non-prepared TX

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTM-1786?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTM-1786: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=978589, https://bugzilla.redhat.com/show_bug.cgi?id=986046 (was: https://bugzilla.redhat.com/show_bug.cgi?id=978589) > Change to TMFAIL for an ABORT on a non-prepared TX > -------------------------------------------------- > > Key: JBTM-1786 > URL: https://issues.jboss.org/browse/JBTM-1786 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JTA, JTS > Affects Versions: 4.16.4 > Reporter: Johnathon Lee > Assignee: Johnathon Lee > > An ABORT on a non-prepared TX should be calling end with TMFAIL. > It's more efficient in that the RM can return an RB* code immediately and short circuit the rollback internally if it likes. More importantly though the RM is less likely to object that it's still running tx activity on another thread and the concurrent TMSUCCESS therefore makes no sense to it. > Also the XAResourceRecord.topLevelAbort code should immediately continue on to calling rollback on the resource despite the failed end(). -- 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

12 years, 8 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 July 2013