camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Kettelerij <>
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

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message