camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Commented: (CAMEL-1738) Memory leak if using JMX and recipientList
Date Mon, 29 Jun 2009 11:58:07 GMT


Claus Ibsen commented on CAMEL-1738:

I guess some endpoints should not consider parameters and others should as they could differ.

The http should obviously not consider parameters.

> Memory leak if using JMX and recipientList
> ------------------------------------------
>                 Key: CAMEL-1738
>                 URL:
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core, jmx
>    Affects Versions: 1.6.0
>         Environment: WinXP, Java 1.6
>            Reporter: Andres
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.0.0
>         Attachments: JConsole.jpg,
> There seems to be a memory leak if you are using recipientList and JMX enabled. The problem
is that endpoint MBean name computed by using hashCode, if there is lot of different endpoints
(created on runtime) every new endpoint will create a new MBean instance. 
> Also in recipientList every entry will create new endpoint. 
> In example if we have 3 urls ; 
>  http://host/index?id=1
> 	http://host/index?id=2
> 	http://host/index?id=3
> Camel will add 3 different MBeans entry to JMX. As url parameters are normally unique
then camel will end up with creating thousands of endpoint entries. But every MBean takes

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message