FAQ
Hi,

We are planning to use camel components without routes (with
consumer/producer templates).
What is the over head of a Camel context? Is it ok to have 10s of
camel contexts. Or should single camel context be shared across different
components within same process?
Please let me know your comment.

With Best Regards,
Diwakar

--
View this message in context: http://camel.465427.n5.nabble.com/Camel-context-tp5523994p5523994.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Search Discussions

  • Vincent Nonnenmacher at Feb 29, 2012 at 2:29 pm
    That a very strange position !

    Can you describe what you are trying to do with just a producer to consumer
    ?
    Is this a simple Message passing between two pojos ?

    If this is the case Camel is overkill for that, and if you are planning to
    have
    several of theses, it means that you have some sort of 'orchestration'
    isn't it ?


    On Wed, Feb 29, 2012 at 5:40 AM, diwakar wrote:

    Hi,

    We are planning to use camel components without routes (with
    consumer/producer templates).
    What is the over head of a Camel context? Is it ok to have 10s of
    camel contexts. Or should single camel context be shared across different
    components within same process?
    Please let me know your comment.

    With Best Regards,
    Diwakar

    --
    View this message in context:
    http://camel.465427.n5.nabble.com/Camel-context-tp5523994p5523994.html
    Sent from the Camel - Users mailing list archive at Nabble.com.
  • Christian Schneider at Feb 29, 2012 at 2:47 pm
    Typically it is better to share a context. That allows for example to
    share a common jms component.
    The memory overhead is not very high but startup time may be an issue if
    you use many camel contexts.

    Christian

    Am 29.02.2012 05:40, schrieb diwakar:
    Hi,

    We are planning to use camel components without routes (with
    consumer/producer templates).
    What is the over head of a Camel context? Is it ok to have 10s of
    camel contexts. Or should single camel context be shared across different
    components within same process?
    Please let me know your comment.

    With Best Regards,
    Diwakar

    --
    View this message in context: http://camel.465427.n5.nabble.com/Camel-context-tp5523994p5523994.html
    Sent from the Camel - Users mailing list archive at Nabble.com.

    --
    Christian Schneider
    http://www.liquid-reality.de

    Open Source Architect
    Talend Application Integration Division http://www.talend.com
  • Ashwin Karpe at Feb 29, 2012 at 2:50 pm
    Hi,

    Can you please describe your use case before soliciting comment on this
    approach...

    It would work just fine in an embedded scenario where Camel behaves more
    like a JCA connector to resources at the backend.

    The Camel Context performs lifecycle operations for entities under its
    control and own resources (aka threads, etc) to support underlying routes,
    components and entities under its direct control. As such the Camel Context
    is fairly benign and is only involved during lifecycle ops and stats
    gathering.

    In this regard, use case detail is directly proportional to response
    quality. Please provide further info.

    Cheers,

    Ashwin...

    -----
    ---------------------------------------------------------
    Ashwin Karpe
    Apache Camel Committer & Sr Principal Consultant
    FUSESource (a Progress Software Corporation subsidiary)
    http://fusesource.com

    Blog: http://opensourceknowledge.blogspot.com
    ---------------------------------------------------------
    --
    View this message in context: http://camel.465427.n5.nabble.com/Camel-context-tp5523994p5525119.html
    Sent from the Camel - Users mailing list archive at Nabble.com.
  • Diwakar at Mar 1, 2012 at 4:22 am
    Hi,

    The context is following
    http://camel.465427.n5.nabble.com/Camel-Components-as-Pojos-td5080073.html#a5080943.
    From the replies I understand that it should be fine to have
    multiple DefaultCamelContext objects.

    With Best Regards,
    Diwakar


    --
    View this message in context: http://camel.465427.n5.nabble.com/Camel-context-tp5523994p5526870.html
    Sent from the Camel - Users mailing list archive at Nabble.com.
  • Babak Vahdat at Mar 1, 2012 at 9:05 am
    Hi

    The thread you're cross-pointing here did *not* claim anything about the
    usage of one single Camel context versus using multiple ones.

    The only concern of that thread was to make it clear that *even* in the
    absence of Camel *routes* you could still benefit from using Camel as it
    would still make life easier for you. For example in the case of
    producing/consuming JMS messages.

    Maybe go once again back to that thread and read all the responses
    *carefully*.

    Babak

    --
    View this message in context: http://camel.465427.n5.nabble.com/Camel-context-tp5523994p5527325.html
    Sent from the Camel - Users mailing list archive at Nabble.com.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupusers @
categoriescamel
postedFeb 29, '12 at 4:40a
activeMar 1, '12 at 9:05a
posts6
users5
websitecamel.apache.org

People

Translate

site design / logo © 2021 Grokbase