| From: Christopher Schultz [mailto:[EMAIL PROTECTED] | Sent: Wednesday, 14 March, 2007 15:02 | | In my tests on the larger machine, the JVM kindly tells me that it can't | give me that much memory, rather than crashing and burning as I would | expect after being tricked by the OS.
Perhaps the JVM calls getrlimit(RLIMIT_AS,...) and just takes the current soft limit as the maximum? It might be interesting to write some code to set the soft limit up to the hard limit and then exec() the JVM to see if that makes a difference. Of course, the result would probably be the crash&burn, but if you're curious... I note that on later Linux kernels you can disable the overcommiting allocation behavior with: # echo 2 > /proc/sys/vm/overcommit_memory ----------------------------------------- ------------------------------------------------------------ The information contained in this message is confidential proprietary property of Nelnet, Inc. and its affiliated companies (Nelnet) and is intended for the recipient only. Any reproduction, forwarding, or copying without the express permission of Nelnet is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this e-mail. ------------------------------------------------------------ --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
