You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2009/09/14 13:11:13 UTC

[jira] Created: (CAMEL-2011) JmsEndpoint - Change it to be singleton

JmsEndpoint - Change it to be singleton
---------------------------------------

                 Key: CAMEL-2011
                 URL: https://issues.apache.org/activemq/browse/CAMEL-2011
             Project: Apache Camel
          Issue Type: Improvement
          Components: camel-jms
    Affects Versions: 2.0.0
            Reporter: Claus Ibsen
            Assignee: Claus Ibsen
            Priority: Minor
             Fix For: 2.1.0


Letting JmsEndpoint be singleton avoids
- overhead of creating new instances when for example a producer template sends to same endpoints
- management is not having overhead of registering 100s of same virtually the same endpoints that binds to the same JMS queue
- potential a little performance gain without the overhead of creating a new JmsEndpoint when needed by getEndpoint

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

[jira] Resolved: (CAMEL-2011) JmsEndpoint - Change it to be singleton

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/activemq/browse/CAMEL-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-2011.
--------------------------------

    Resolution: Fixed

trunk: 814584.

> JmsEndpoint - Change it to be singleton
> ---------------------------------------
>
>                 Key: CAMEL-2011
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2011
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-jms
>    Affects Versions: 2.0.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> Letting JmsEndpoint be singleton avoids
> - overhead of creating new instances when for example a producer template sends to same endpoints
> - management is not having overhead of registering 100s of same virtually the same endpoints that binds to the same JMS queue
> - potential a little performance gain without the overhead of creating a new JmsEndpoint when needed by getEndpoint

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