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

Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2017/05/01 02:01:04 UTC

[jira] [Commented] (ARTEMIS-469) Artemis needs PoolingConnectionFactory for standalone clients

    [ https://issues.apache.org/jira/browse/ARTEMIS-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15990539#comment-15990539 ] 

Justin Bertram commented on ARTEMIS-469:
----------------------------------------

The pooled connection factory component from the 5.x code-base can be used with Artemis as is. It just needs to be configured properly. 

Of course, it doesn't support JMS 2.0. Implementing JMS 2.0 for the pooled connection factory is the only compelling value-add I can see for porting it over to the Artemis code-base.

> Artemis needs PoolingConnectionFactory for standalone clients
> -------------------------------------------------------------
>
>                 Key: ARTEMIS-469
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-469
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>          Components: Broker
>         Environment: Solaris
>            Reporter: Abhijith Prabhakar
>
> Artemis does not have PoolingConnectionFactory which can be used outside of container in standalone applications.  More on conversation here:  http://activemq.2283324.n4.nabble.com/Apache-Artemis-pooling-td4707663.html#a4707675
> Similar to ActiveMQ, Artemis needs a standalone PoolingConnectionFactory which is built on JMS 2.0 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)