Hi Daniel, I don't believe your problems are just load related no. Both Matt and I have asked questions about your application without you giving some information about what the app is doing we're not going to be able to help.
1. Matt points out that there was a known memory leak around XMLSearch against XML objects stored in the application scope. 2. I pointed out that sessions which store persisted CFCs can be problematic if you have a large number of sessions and depending on the size of your objects. Broadly speaking either 1. Its a leak or some other bug 2. Its the app scope or a cache getting too much data shoved in it 3. You have too much data in session But as both of us have said you need to share more info or its just guess work. Many thanks Alex On Oct 10, 8:38 am, Daniel Eng <[email protected]> wrote: > Hi guys, > > This is an old thread... but the problem still persists in my server. I get > an 503 Error every 4-6 hours. > > Do you think it's still load related? > > I have been updating the Apache Tomcat OpenBD Properties - Java Tab. and > Change the Initial Memory Pool to 1GB. And the Maximum Memory Pool to 4GB. > > Also the Thread Stack Size to 256KB. > > Is that sufficient? How do I findout for sure what is the problem? > > Appreciate your help! > > Daniel > > On Sat, Jul 30, 2011 at 11:53 PM, Matthew Woodward > <[email protected]>wrote: > > > > > > > > > On Sat, Jul 30, 2011 at 8:18 AM, Daniel Eng <[email protected]> wrote: > > >> Have anyone tried these before? What did you guys set for your memory > >> setting? > > > Memory settings completely depend on the application's needs, really. Just > > as a ballpark for the max heap size, if I'm not running much else on a > > server other than Tomcat, I'll give Tomcat 2GB max heap on a 64-bit system > > with 4GB of RAM (we run everything on VMs these days so we tend to have a > > high number of small-ish VMs as opposed to a smaller number of monster > > boxes), and that seems to work well. > > >> I tried changing the setting in the Apache Tomcat OpenBD Properties under > >> the Java tab. Increased the setting for Initial Memory Pool to 1GB and the > >> Maximum Memory Pool to 2GB. > > > Depending on what your app is doing, load, etc. that's at least a > > respectable amount of RAM. > > >> I noticed that I have less downtime... but it still happens. What's the > >> best way to beat this? > > > Well, it's entirely possible that it's load related, you may have a slow > > memory leak in your code, and you didn't mention what your MaxPermGen > > setting was, which isn't the same as heap space of course but knowing that > > setting will provide a more complete picture. > > > It'd also be interesting to see more of the stack trace to see where > > specifically things choke and if it's the same thing every time ... can you > > share more the full stack trace on pastebin.com (i.e. don't send it to the > > list since it might be huge). > > > Also if there's anything specific about the application you can share > > that'd be helpful. For example there was an issue on OpenBD 1.4 (which I > > assume is what you're running) related to XML in the application scope, so > > sharing the basics of what your application is doing will provide more > > clues. > > -- > > Matthew Woodward > > [email protected] > >http://blog.mattwoodward.com > > identi.ca / Twitter: @mpwoodward > > > Please do not send me proprietary file formats such as Word, PowerPoint, > > etc. as attachments. > >http://www.gnu.org/philosophy/no-word-attachments.html > > > -- > > official tag/function reference:http://openbd.org/manual/ > > mailing list -http://groups.google.com/group/openbd?hl=en -- official tag/function reference: http://openbd.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en
