camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Kettelerij <richardkettele...@gmail.com>
Subject Re: catching OutOfMemoryError on the route
Date Fri, 18 Mar 2011 21:14:51 GMT
Catching OutOfMemoryErrors using try/catch isn't the way to go. Like Taariq I
advice monitoring your app and make heap dumps for memory analysis purposes. 

A tip: If you add -XX:+HeapDumpOnOutOfMemoryError as a JVM startup parameter
you can have JVM automatically create a heap dump in the unfortunate case an
OutOfMemoryError occurs. See
http://www.oracle.com/technetwork/java/javase/memleaks-137499.html#gdyrr.

--
View this message in context: http://camel.465427.n5.nabble.com/catching-OutOfMemoryError-on-the-route-tp3962278p3985770.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message