This content has been marked as final.
Show 4 replies
-
1. Re: JVM Crash on Xen
peterj Nov 9, 2009 2:38 PM (in response to robshep)Since it is a JVM crash, you should talk to the JVM vendors. Of course, they will probably blame it on Xen, so you will have to get those people involved also. Good luck. Too bad you aren't using RHEL with a support contract... (Or perhaps you have a support contract for Ubuntu?)
-
2. Re: JVM Crash on Xen
peterj Nov 9, 2009 2:43 PM (in response to robshep)One more thought - try setting min and max heap size to the same value and see if that helps.
-
3. Re: JVM Crash on Xen
robshep Nov 10, 2009 7:29 AM (in response to robshep)Thanks Peter,
Xms == Xmx shows no difference.
Odd numbers though.
1791 MB jvm crashes
1792 MB (1.75000 GB) stable.
No other Java programs are affected, only JBoss.
Does JBoss do some memory manipulation, or populate some large datastructures at startup?
Thanks
Rob -
4. Re: JVM Crash on Xen
peterj Nov 10, 2009 10:19 AM (in response to robshep)No other Java programs are affected
Can I assume that you run those other Java programs also with heaps of 1792MB or greater?Does JBoss do some memory manipulation, or populate some large datastructures at startup?
No pure Java app can manipulate memory - all it can do is allocate objects, it is the JVM that asks for memory and the OS that allocates the memory to the app as needed. Also, I was working with a customer a few weeks ago who was trying to pin down some memory leaks and for the web services that had no such leaks we were down to a 64MB heap and still never got an OOME, so I would say no, JBoss AS does not allocate large data structures at startup. It does, however, call System.gc() a few times during startup which causes a major collection and the JVM always "readjusts" the memory during major collections. I suspect that the crash happens during one of those readjustments.