This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
There is certainly an upper limit to the amount of memory a single JVM instance can get from the operating system, but no special limits that apply to web applications only. How much memory are you currently giving to Tomcat? Bill
Joined: Oct 12, 2000
I'm not responsible for the server configuration, given the knowledge of the person who is I doubt it's changed much from the defaults (he's no Java expert, but a Unix and database person).
At the moment things are still working but seem to be slowing down a bit (which could well be because the harddisk is running out of space which I discovered earlier this week when the compiler complained about "disk full").
Author and all-around good cowpoke
Joined: Mar 22, 2000
If your program is getting that big but still running with Tomcat defaults, no wonder it is slowing down.
You might stick in some memory monitoring code accessed by a password protected request. This is a great way to track your application remotely and need not be too complex. For example, I use this sort of "back door" to get a histogram of response times, post emergency messages to users ("system going down in 5 minutes!") and check other usage statistics. Bill