Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311160 - HeapDumpContributorTests dumpHeap fails
Summary: HeapDumpContributorTests dumpHeap fails
Status: CLOSED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: unknown (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Steve Powell CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-30 07:29 EDT by Steve Powell CLA
Modified: 2010-05-06 08:56 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Powell CLA 2010-04-30 07:29:02 EDT
junit.framework.AssertionFailedError: expected:<false> but was:<true>
	at org.eclipse.virgo.medic.dump.impl.HeapDumpContributorTests.dumpHeap(HeapDumpContributorTests.java:64)

This line expects there NOT to be a dump file (heap.out), but 
org.eclipse.virgo.medic.dump.impl.heap.HeapDumpContributor 
in project org.eclipse.virgo.medic.core
writes heap.out even if a heap dump is NOT generated.
Comment 1 Steve Powell CLA 2010-04-30 07:31:05 EDT
Solution is to modify HeapDumpContributor to NOT generate a file called "heap.out" when it hasn't generated a heap file.
Comment 2 Steve Powell CLA 2010-05-05 10:06:51 EDT
Solution (comment 1) implemented.  Heap dump not reliably taken.  Long term solution requires better heap dump implementation in multiple JVMs.
Comment 3 Steve Powell CLA 2010-05-06 08:56:12 EDT
[Bug: 311858] was raised when this fix caused other tests to fail.

That issue is now settled. This one can be closed.