Peter Schuller wrote:
>
> > It seems there is some memory leak in the HotSpot of IBM JVM.
>
> HotSpot is a Sun thing; there is no "HotSpot" in IBM's JVM.
To be pandantic, HotSpot is a java Just-in-time compiler, aka JIT.
IBM's JVM also has a JIT, it just has a different name, and it's
on by default. IBM requires an -option at runtime to disable it.
>
> What are your threads doing?
I don't have any threads in my app, just the main thread and the usual
event queue/etc threads provided by java. The problem is that simply
launching an app under an IDE debugger causes the debuggee to dump
core before it actually loads any classes.
> While IBM's JDK is pretty good, it seems to
> have a bad GC; it throws OutOfMemoryErrors a bit too easy.
>
> And exactly how does it "crash"?
IBM's JVM dumps core with SEGV errors. Consistantly.
When I posted a polite query about it on their newsgroup, they canceled
my post. :p
>
> > Who can give me suggestions to control the heap size of JVM?
> > My system is Redhat 6.2.
>
> -Xmx and -Xms. "java -X" for more info.
--
Joi Ellis Software Engineer
Aravox Technologies [EMAIL PROTECTED], [EMAIL PROTECTED]
No matter what we think of Linux versus FreeBSD, etc., the one thing I
really like about Linux is that it has Microsoft worried. Anything
that kicks a monopoly in the pants has got to be good for something.
- Chris Johnson
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
