[
https://issues.jboss.org/browse/GTNPORTAL-3500?page=com.atlassian.jira.pl...
]
Trong Tran updated GTNPORTAL-3500:
----------------------------------
Attachment: TestDownloadService.java
It's not easy to reproduce the issue actually. However, I have made some changes to
get the problem occurred more frequently (attached test case)
The root problem is that it's using ConcurrentFIFOExoCache for holding resources
temporarily. This test is to assert the cached objects size == max size BUT in the case of
multi-threading, it can not be 100% sure that cacheSize == maxSize at any time as it needs
a little time to execute the cache eviction. ===> for me, it's normal
I think we could deactivate the usecase. if we consider this is a real case, we could
create an issue in eXo Kernel instead.
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
Attachments: TestDownloadService.java
Original Estimate: 1 day, 4 hours
Time Spent: 4 hours
Remaining Estimate: 1 day
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.3#6260)