Dears,
I think I found the culprit.
I did not mentioned that in the same application,we are using also
Spring-Batch runtime (through JSR API). The Spring context of the
Spring-Batch is inheriting of a common shared context to allow the usage of
some bean in the jobs definition. But since we are
Dears,
I have a strange issue.
I have an JEE application (ear) that I deployed on a Frontend servers (2)
and Backend servers (2). The same ear is deployed on all servers and a
property file is used to activate or not the components and or camel routes
on particular servers.
I am using Camel
Dear Claus,
I think you spotted exactly the issue. Therefore I will wait for the new
release 8-).
Thanks a lot,
Cataldo.
--
View this message in context:
http://camel.465427.n5.nabble.com/JMX-Management-tp550p555.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Claus,
Sorry I forgot to mention it!
This is the 2.16.2 and i am deploying in Weblogic 12.1.1.
Br,
Cataldo.
--
View this message in context:
http://camel.465427.n5.nabble.com/JMX-Management-tp550p552.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Dears,
I activated the JMXAgent for monitoring purpose.
But I have a problem because I am using a JPA endpoint as 'TO' (defined as
XML route), and when the route is activated, it creates a new instance of
JPAProducer and it is visible via JMX but when is not more used is stays
register as mbean
Dears,
One interresting thing.
When I disable the JMX agent the jpaProducer instances are released and
garbage collected.
It seems to me that is the JMX agent is keeping reference on the JpaProducer
objects making them never released.
Now I am wondering if it is a misconfiguration or it is a
Dears,
I am using the JPA component to persist some messages into a DB table on
which multiple JPA consumers will consume enrich to send them after in
aggregator.
The routes are expressed exclusively in XML (spring-camel). From the point
of view of the routes everything seems to work well.
To
