0x0E Bitsraised in a barn by hippy wolves

Fri Sep 19 13:34:00 CDT 2008

We have a java program (java 5 VM) that we are starting up with -Xmx1500m. Occasionally, if the machine has been running for several days, java will fail to start with a message along the lines of "cannot start VM, unable to allocate heap". This is on a Windows XP machine. If I reboot the machine, the process starts without problems. If I look at free memory using sysinterals process explorer, in both cases I see sufficient available physical memory to satisfy the request, so I suspect that the problem is that the Windows memory space has become fragmented.

Do you have any suggestions for ways that I can 1) confirm that suspicion and/or 2) solve the problem without rebooting the machine on some regular basis?

Have you heard other reports of this?