[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
[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
[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