• Post Reply Bookmark Topic Watch Topic
  • New Topic

"Java HotSpot(TM) 64-Bit Server VM warning: Attempt to allocate stack guard pages failed." anyone?

 
Elhanan Maayan
Ranch Hand
Posts: 136
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i'm getting this warning several times on our logs, doing dmesg on 'killed process' indicates java process has been killed several times .

this is running on a vm, and the xmx is usually set to take entire machine's allocated memory minus 1gb .
 
Tim Holloway
Bartender
Posts: 18412
58
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't have hard numbers, but every indication I've seen is that "mx" is merely the amount of memory allowed for Java objects themselves. That is, not including stuff like the core JVM and possibly secondary constructs like buffers and the like.

I recommend tracking the TOTAL RAM usage on the machine on a running basis using something like vmstat and at least occasionally "top". If the xm allotment exceeds actual available RAM, I'm pessimist enough to expect that the entire JVM may blow, not just throw OutOfMemory exceptions.

It wouldn't hurt to check to see if any dumpfiles were produced, though. A post-mortem might turn up a bug in the JVM or something.
 
Elhanan Maayan
Ranch Hand
Posts: 136
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
No dump were produced, this is because they JVM didn't die from OutOfMemory Exception but rather the oom killed the dmesg indicates the total-vm was like 10gb while the anon-rss was 7.8 of the process that was killed.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!