Win a copy of The Way of the Web Tester: A Beginner's Guide to Automating Tests this week in the Testing forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Tomcat OutOfMemory Exception

premesh purayil
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My app seems to have memory leak i would assume. Its basically an abstraction ontop of a database but when i run unit tests on a client application which calls out to this service it eventually yacks. If i run the unit test classes individually its fine (although after a number of them i run into the same problem) but if i run the whole suite (350 tests) its bombs out on the same test every time... ( that test basically causes one write and a read from the underlying DB). Whats the best way to tack where my problem specifically? takes 45 mins of unit tests to replicate this and setting breakpoints searching for the problem has been VERY difficult... suggestions?
here is the stack trace..
0060111|094336062|14|SEVERE|caught throwable
20060111|094337504|15|SEVERE|Exception invoking periodic operation:
20060111|094345516|13|SEVERE|caught throwable
20060111|094349862|11|SEVERE|caught throwable
ERROR: 'null'
FATAL ERROR: 'Could not compile stylesheet'
20060111|094353197|14|SEVERE|JAXRPCTIE01: caught exception while handling reques
t: javax.xml.rpc.soap.SOAPFaultException: Unable to dump SOAPMessage
20060111|094355140|13|SEVERE|caught throwable
20060111|094401369|11|SEVERE|caught throwable
20060111|094404424|13|SEVERE|caught throwable
20060111|094405776|14|SEVERE|caught throwable
20060111|094407859|13|SEVERE|caught throwable
20060111|094410212|14|SEVERE|caught throwable
20060111|094412355|13|SEVERE|caught throwable
20060111|094414158|11|SEVERE|caught throwable
20060111|094417233|13|SEVERE|caught throwable
20060111|094417233|11|SEVERE|Caught exception (java.lang.OutOfMemoryError) execu
ting, terminating thread
20060111|094432595|15|SEVERE|Exception invoking periodic operation:
20060111|094440557|14|SEVERE|caught throwable
20060111|094442610|13|SEVERE|caught throwable
20060111|094444353|14|SEVERE|caught throwable
20060111|094445925|13|SEVERE|caught throwable
20060111|094537481|15|SEVERE|Exception invoking periodic operation:
20060111|094648857|15|SEVERE|Exception invoking periodic operation:
20060111|094800302|15|SEVERE|Exception invoking periodic operation:
20060111|094911648|15|SEVERE|Exception invoking periodic operation:
20060111|094952859|15|SEVERE|Exception invoking periodic operation:
William Brogden
Author and all-around good cowpoke
Posts: 13074
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think that if this was my problem I would first try to use the Tomcat Management Application to monitor Tomcat memory use and Thread count. Tomcat 5 has quite a nice browser interface for this.
For example, I discovered an app that was putting each request Thread in an infinite loop and thus consuming memory.
Balaji Loganathan
author and deputy
Posts: 3150
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am moving this to our Tomcat forum. Please continue ur discussion there.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic