camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zach Calvert (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5058) Bug: Unique Endpoints Leaking in DefaultInflightRepository
Date Tue, 06 Mar 2012 13:04:57 GMT


Zach Calvert commented on CAMEL-5058:

Claus, that is correct that I'm using the producer template to send the messages.  I actually
have a solution that I'm currently testing, but I've got to wait for our legal department
to review the change to submit back to the community (we've got a big process I have to follow).

Hopefully I will be able to submit the patch, including a unit test, to validate the change.
> Bug: Unique Endpoints Leaking in DefaultInflightRepository
> ----------------------------------------------------------
>                 Key: CAMEL-5058
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.9.0
>            Reporter: Zach Calvert
>            Assignee: Claus Ibsen
>             Fix For: 2.10.0, 2.9.2
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> If you have an endpoint protocol which uses unique URIs you will leak Strings in the
HashMap stored in the DefaultInflightRepository (org.apache.camel.impl.DefaultInflightRepository)
> It seems there is a reference counting scheme in place, but it doesn't do a remove until
the "stop" method is called to shut the system down.  We are running XMPP endpoints, which
use a protocol like xmpp://someaccount@domain/password?to=someOtherAccount
> When there are 10 million accounts, not all of which are active, but all of which may
message at some time or another, no references are removed to the endpointCount.
> When the count becomes 0, the reference should be removed and the size method will still
return the appropriate result.
> Please be careful in the implementation to synchronize on some object (perhaps the AtomicInteger)
reflecting a read/write lock on the endpoint count modification.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message