Hi,
In my point of view, the problem is not in camel : a dump of JVM memory
shows that created objects (org.apache.cxf.phase.
PhaseInterceptor*) are retained by the ConcurrentHashMap that is
instanciated by a class in CXF code
(org.apache.cxf.clustering.FailoverTargetSelector).
Those objects are
The CXF fail-over target selector appears to be cleaning up its state
properly, which also implies the actual clients properly complete the
exchanges, I've tried WS RS failover tests on the trunk.
Indeed, try upgrading somehow and see if it persists
Sergey
On 18/12/13 09:43, LORENZA Adnan
Hi,
I developed a camel cxf component that is configured to failover to
alternate addresses in case of connections /availability failures.
The camel component is a simple timer that sends every second a request to
a webservice.
The camel route is the following :
public void configure() throws
Hi,
Your camel version is quite old (it is about two years old), and we don’t
provide community support for that version.
Can you try to run the test with some latest released Camel ?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog:
Hi Willem,
Thanks for this quick answer.
My camel component is deployed on a jbi servicemix-fuse-3.5-00.
If I upgrade my component to Camel 2.12 do you think that I can deploy it
on servicemix 3.4 or servicemix-fuse-3.5-00 ?
Thanks
On Tue, Dec 17, 2013 at 10:27 AM, Willem Jiang
Hi,
It not easy to upgrade the camel version in the service.
You can using Main[1] or camel:run maven plugin[2] to start your route.
It could more easy to verify if the memory leak issue still there.
[1]http://camel.apache.org/running-camel-standalone-and-have-it-keep-running.html
