Just prior to posting my question, I changed some things with my DB
connection pool, and the system has been running for more than a day. Which
is 100% better than it has run (over the last month).
Could this have been caused by a poorly configured (default) thread pool
profile? In turn, hiding
These are just a couple, the first is an example of a producing route, the
second it one of the processing routes.
Thanks for looking!
Mark Webb wrote
Could you post your route definitions?
--
View this message in context:
I'm running Camel (2.14.1) on ServiceMix (5.4.0), and have 21 routes across
two bundles, including 11 timer producing endpoints.
After around 10 hours (~1000 timer messages) of running, camel grinds to a
halt, and only restarting the bundles resolves the issue. I have placed .log
processors
