[gatein-issues] [JBoss JIRA] (GTNPORTAL-3500) testMemoryLeakWithMultiThread fails sometimes

RH Bugzilla Integration (JIRA) issues at jboss.org
Fri Jun 20 15:29:24 EDT 2014


    [ https://issues.jboss.org/browse/GTNPORTAL-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978270#comment-12978270 ] 

RH Bugzilla Integration commented on GTNPORTAL-3500:
----------------------------------------------------

Peter Palaga <ppalaga at redhat.com> changed the Status of [bug 1103304|https://bugzilla.redhat.com/show_bug.cgi?id=1103304] from NEW to MODIFIED

> testMemoryLeakWithMultiThread fails sometimes
> ---------------------------------------------
>
>                 Key: GTNPORTAL-3500
>                 URL: https://issues.jboss.org/browse/GTNPORTAL-3500
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>            Reporter: Peter Palaga
>            Assignee: Trong Tran
>             Fix For: 3.9.0.Final
>
>         Attachments: TestDownloadService.java
>
>   Original Estimate: 1 day, 4 hours
>          Time Spent: 1 day
>  Remaining Estimate: 0 minutes
>
> Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1103304
> org.exoplatform.download.TestDownloadService.testMemoryLeakWithMultiThread() fails in some cases. The stack trace:
> junit.framework.AssertionFailedError
> 	at junit.framework.Assert.fail(Assert.java:48)
> 	at junit.framework.Assert.assertTrue(Assert.java:20)
> 	at junit.framework.Assert.assertTrue(Assert.java:27)
> 	at org.exoplatform.download.TestDownloadService.testMemoryLeakWithMultiThread(TestDownloadService.java:109)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ...
> The line where it fails is 
> assertTrue(cache.getCacheSize() <= 10);
> Version-Release number of selected component (if applicable):
> GateIn 3.8.x or 3.9.x
> Reproducible sometimes: 1/10 or even less. Happens both on Jenkins and desktop.
> Steps to Reproduce:
> Not sure. It happens randomly. Perhaps overloading the machine with some CPU-intensive task might help. Just build the exo.portal.component.web.server artifact with tests repeatedly until it fails.
> Actual results:
> Test fails
> Expected results:
> Not sure if the subject under the test is broken or the test itself.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


More information about the gatein-issues mailing list