This is related to a forum thread called "LRUCache memory leak when using
camel properties file" and fix [CAMEL-4261] - Properties component - Cached
locations may add duplicates.
I finally had some time to download Camel 2.8.1 and do some testing to see
if the fix corrected my problem. I am st
Hi Claus,
Thanks for your response. I now understand why I was experiencing blocking.
However, I would like to advocate that the default threadpool for wireTaps
not use the caller run rejection policy. This default policy works well
for splits and other mechanisms, but I don't believe it is us
I have a wireTap in a route (route A) and the wireTap creates a new message
and is directed to a new route (route B).
A -> WT -> to(dest) |
\/
B
B -> to(jms:queue:output) -each thread in the pool with hang if the
jms queue is full
If B is pub
Claus,
Thanks for identifying this. I have removed the properties from my
camelContext.xml file and the memory leak has vanished. Can you make this
correction 2.8.0 or 2.8.1?
Bret
--
View this message in context:
http://camel.465427.n5.nabble.com/LRUCache-memory-leak-when-using-camel-properti
I'm using camel 2.7.1
here is a piece of my camelContext.xml file that is having the problem.
>From what I can tell, the problem is occurring inside the tags and
that it is being exacerbated by the one to many activities associated with
the split. It looks like the split is creating a separat
I'm presently using properties to populate my camelContext.xml file and my
camel spring container is running out of memory consistently. When I use
MAT to evaluate the heap dump files it points to LRUCache in the
org.apache.camle.component.properties.PropertiesComponent as the problem.
It appea
