[jira] Commented: (CAMEL-1738) Memory leak if using JMX and recipientList

["Andres (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/CAMEL-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52393#action_52393 ] 

Andres commented on CAMEL-1738:
-------------------------------

Temporary workaround that works for me is  to overwrite CamelNamingStrategy via custom lifecycleStrategy bean.

My custom CamelNamingStrategy overwrites getEndpointId and computes EndpointId so that url parameters not considered.

> Memory leak if using JMX and recipientList
> ------------------------------------------
>
>                 Key: CAMEL-1738
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1738
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.6.0
>         Environment: WinXP, Java 1.6
>            Reporter: Andres
>            Priority: Minor
>         Attachments: JConsole.jpg, MemLeak.java
>
>
> 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 memory.

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