Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.218.215 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=RihKfA85mg/ZWvFGSEE2WvYxMqIYJZeK6wLmrGjV0elZvRJGktCRi7CbM1OANndzE3
         iWHYln4Q4nXmJKiNEptneHQwrWITdUbDfcmTZjbC2deBHduE9+XCMTQnueauhcTtIGaH
         izKnUNiFbrzXkKKtSqtG5Pk3QdkY+HoBONBFY=
MIME-Version: 1.0
In-Reply-To: <28219199.post@talk.nabble.com>
References: <28219199.post@talk.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Tue, 13 Apr 2010 09:15:42 +0200
Message-ID: <p2k5380c69c1004130015p3e10d1abgb01942bc996feac2@mail.gmail.com>
Subject: Re: Injecting ProducerTemplates, scoping, and JMX memleak
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 13, 2010 at 1:22 AM, matthewm <mmoaot@gmail.com> wrote:
>
> Hello,
>
> We are using Camel 2.2.0 with Spring 3.0.1.RELEASE in the context of a we=
b
> service.
>
> We've been using @EndpointInject to inject ProducerTemplates into our bea=
ns.
> Some of our beans are request scoped, and so a new ProducerTemplate is
> created and injected on each request.
>
> After more study this seems to run counter to the idea of ProducerTemplat=
e,
> which appears to have been conceived as a long-lived object rather than
> transient. =A0It seems perhaps the documentation of @EndpointInject might
> point this out; injecting into singletons makes perfect sense but injecti=
ng
> into request-scoped beans may be undesirable.
>

The FAQ has some details on producer template
http://camel.apache.org/why-does-camel-use-too-many-threads-with-producerte=
mplate.html

You can just use @Autowired or other Spring IoC stuff.

@Autowired
private ProducerTemplate template;

Camel will automatic enlist a ProducerTemplate if you do not explict
set a <template id=3D"xxx"/> in the <camelContext/> tag.
Then it will use the shared instance of ProducerTemplate instead of
creating a new one each time.


> Specifically, the issue we found is that each ProducerTemplate creates a
> Producer which then is registered with JMX. =A0Eventually we wind up with
> thousands of Producers referenced by JMX (but otherwise garbage) resultin=
g
> in OOM errors.
>

Yeah this is fixed in 2.3-SNAPSHOT.

> It seems like a bug that Camel's JMX integration prevents producers from
> being eligible for GC. =A0But how best to proceed with making a
> ProducerTemplate available to request scoped beans?
>
> Thanks!
>
> Matt
> --
> View this message in context: http://old.nabble.com/Injecting-ProducerTem=
plates%2C-scoping%2C-and-JMX-memleak-tp28219199p28219199.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>


--=20
Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus