September 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1716) BACoordinatorCompletionTest test hung

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1716?page=com.atlassian.jira.plugin.... ] Tom Jenkinson edited comment on JBTM-1716 at 9/17/13 6:13 AM: -------------------------------------------------------------- Hanging on container stop: {quote} "Main" at org.jboss.arquillian.container.impl.ContainerImpl.stop(ContainerImpl.java:217) {quote} Looks like a duplicate of JBTM-1919 was (Author: tomjenkinson): Hanging on container stop: {quote} "Main" at org.jboss.arquillian.container.impl.ContainerImpl.stop(ContainerImpl.java:217) {quote} Looks like a duplicate of JBTM-1912 > BACoordinatorCompletionTest test hung > ------------------------------------- > > Key: JBTM-1716 > URL: https://issues.jboss.org/browse/JBTM-1716 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Trivial > Fix For: 5.0.0.M5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > org.jboss.narayana.txframework.functional.ws.ba.coordinatorCompletion.BACoordinatorCompletionTest test hung. > See here for log: http://172.17.131.2/job/narayana/TESTS=XTS,jdk=jdk7.latest,label=linux/63... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1716) BACoordinatorCompletionTest test hung

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1716?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1716: ------------------------------------- Hanging on container stop: {quote} "Main" at org.jboss.arquillian.container.impl.ContainerImpl.stop(ContainerImpl.java:217) {quote} Looks like a duplicate of JBTM-1912 > BACoordinatorCompletionTest test hung > ------------------------------------- > > Key: JBTM-1716 > URL: https://issues.jboss.org/browse/JBTM-1716 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Paul Robinson > Assignee: Amos Feng > Priority: Trivial > Fix For: 5.0.0.M5 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > org.jboss.narayana.txframework.functional.ws.ba.coordinatorCompletion.BACoordinatorCompletionTest test hung. > See here for log: http://172.17.131.2/job/narayana/TESTS=XTS,jdk=jdk7.latest,label=linux/63... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1921) @Provider annotation is missing on org.jboss.narayana.rest.bridge.inbound.EJBExceptionMapper

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1921?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-1921: --------------------------------------- Annotation allows provider to be found automatically. It's not a problem for the subsystem, since I'm doing it manually anyway. But if you would like to run it standalone, annotation would be useful. Also I wanted to put the annotation when I wrote the class in the first place, but just forgot about it. Another exceptions mapper has the annotation. > @Provider annotation is missing on org.jboss.narayana.rest.bridge.inbound.EJBExceptionMapper > -------------------------------------------------------------------------------------------- > > Key: JBTM-1921 > URL: https://issues.jboss.org/browse/JBTM-1921 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Trivial > Fix For: 5.0.0.M5 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1921) @Provider annotation is missing on org.jboss.narayana.rest.bridge.inbound.EJBExceptionMapper

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1921?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1921: ------------------------------------- Gytis, can you explain what problems this causes when this is absent and why adding the annotation is the right thing to do. > @Provider annotation is missing on org.jboss.narayana.rest.bridge.inbound.EJBExceptionMapper > -------------------------------------------------------------------------------------------- > > Key: JBTM-1921 > URL: https://issues.jboss.org/browse/JBTM-1921 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Trivial > Fix For: 5.0.0.M5 > > -- 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, 6 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: ----------------------------------------------- mark yarborough <myarboro(a)redhat.com> changed the Status of [bug 968125|https://bugzilla.redhat.com/show_bug.cgi?id=968125] from VERIFIED to CLOSED > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1927) Pull request checker on Windows always reports BlackTie tests as failing

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1927?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1927: -------------------------------- Assignee: Tom Jenkinson (was: Gytis Trikleris) > Pull request checker on Windows always reports BlackTie tests as failing > ------------------------------------------------------------------------ > > Key: JBTM-1927 > URL: https://issues.jboss.org/browse/JBTM-1927 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > > Pull: https://github.com/jbosstm/narayana/pull/429 > Build failed "http://172.17.131.2/job/btny-pulls-narayana-windows2008/293/" > If you look at the report, it is blue with "BUILD SUCCESSFUL" reported: > http://172.17.131.2/job/btny-pulls-narayana-windows2008/293/console -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1927) Pull request checker on Windows always reports BlackTie tests as failing

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1927?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1927: ------------------------------------- Its possible build number 293 was reused by Jenkins, hence one of the runs may have had a failure but we do not have the log for it still > Pull request checker on Windows always reports BlackTie tests as failing > ------------------------------------------------------------------------ > > Key: JBTM-1927 > URL: https://issues.jboss.org/browse/JBTM-1927 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Critical > > Pull: https://github.com/jbosstm/narayana/pull/429 > Build failed "http://172.17.131.2/job/btny-pulls-narayana-windows2008/293/" > If you look at the report, it is blue with "BUILD SUCCESSFUL" reported: > http://172.17.131.2/job/btny-pulls-narayana-windows2008/293/console -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1926) Pull request checker has it in for BlackTie

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1926?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1926: ------------------------------------- Its possible that 1112 was executed twice by CI and so one of the 1112 runs had a blacktie issue. > Pull request checker has it in for BlackTie > ------------------------------------------- > > Key: JBTM-1926 > URL: https://issues.jboss.org/browse/JBTM-1926 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 5.0.0.M5 > > > Comment on pull "Tests failed (http://172.17.131.2/job/btny-pulls-narayana/1112/): BlackTie build failed" > Looked at: http://172.17.131.2/job/btny-pulls-narayana/1112/consoleText, BlackTie was fine, it was txframework that had the 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1926) Pull request checker has it in for BlackTie

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1926?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1926: -------------------------------- Assignee: Tom Jenkinson (was: Gytis Trikleris) > Pull request checker has it in for BlackTie > ------------------------------------------- > > Key: JBTM-1926 > URL: https://issues.jboss.org/browse/JBTM-1926 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 5.0.0.M5 > > > Comment on pull "Tests failed (http://172.17.131.2/job/btny-pulls-narayana/1112/): BlackTie build failed" > Looked at: http://172.17.131.2/job/btny-pulls-narayana/1112/consoleText, BlackTie was fine, it was txframework that had the 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

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1928) Add last x00 lines of build log in the comment when a pull fails

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1928: ----------------------------------- Summary: Add last x00 lines of build log in the comment when a pull fails Key: JBTM-1928 URL: https://issues.jboss.org/browse/JBTM-1928 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Tom Jenkinson Assignee: Gytis Trikleris Priority: Minor Fix For: 5.0.0.M5 It would be useful for external contributors if when the pull request fails, the comment included the last few hundred lines of output so that it might provide some context to the issue. As it stands an internal engineer has to check the log -- 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, 6 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 September 2013