I'm having a problem with a particular application that grows and grows in size until the jvm runs out of memory, and tomcat shuts down. I am on a box with 1GB of memory and 350MB+ of swap. I have tried various settings in my catalina.sh, which just seem to make the app crash even quicker. I suspect that the problem lies in my code, but I don't know exactly where to start looking.
Of course, I don't expect anyone to debug my code, but I'm hoping someone can give me some general hints about things to look for, problems that a relatively new java programmer may be overlooking. For instance, as a c programmer, I am highly (too highly) familiar with memory leaks, and I have seen references to leaking memory in java apps, but in my naivete, I can't really understand what this means, since I neither allocate or free memory anymore. What kind of code constructs cause memory to leak in java? I have some listener classes in my app. Are they a problem? Sessions? Database connections (no pooling)? Any of these things red flags?
Thanks in advance for anything you may have to offer!
tomcat 4.1.18, classes12.jar (from oracle), and xmlparserv2.jar (also oracle)
java version 1.4.0_00
solaris 9 (SunOS 5.9)
Cheers!
Bill
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
