Re: [Wrapper-user] JVM hang - Xms / Xmx

[Leif M. <le...@ta...>]

Paul,

Paul Casanova wrote:

>I tried adding -Xrunhprof:depth=8 to the config file, but the JVM always
>suffers a runtime error r6017 ("unexpected multithread lock error") and
>restarts.  Any ideas?
>  
>
Doing a Google search on that error message.  It looks like a C runtime 
error.
In other words, Java is having a bad day.

Searching the Sun Bug database, the following issue came up:
http://developer.java.sun.com/developer/bugParade/bugs/4724252.html

That bug says it has been fixed in Java 1.4.1.  But the original post 
says that it not
been a problem in 1.3.1_04.  That just means that their app had not been 
able to
reproduce it however.

>Tried starting with initial heap size of 100MB and it took around the same
>time to start as normal, but when I added the -Xrun... it started doing
>full GC's when starting up the app, so it took longer.  Mind you, before I
>added -Xrun... it was doing around 10 GC's (not full) during startup with
>100MB initial!!
>
>Does -Xrunhprof usually have such overhead / impact?
>  
>
Profiling takes a bunch of memory and also has a very noticeable effect of
performance.  Depending on the application of course, but it is usually 
still
usable if you normally have enough CPU / Memory to spare.

Most likely your app is using a bunch more memory than normal and is thus
having problems hitting some upper memory limit.   Have you tried increasing
the max memory setting?   If that is not possible, is it possible to 
test with a
smaller data set?

Cheers,
Leif