[
https://issues.apache.org/jira/browse/QPIDJMS-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322554#comment-16322554
]
Timothy Bish edited comment on QPIDJMS-353 at 1/11/18 4:58 PM:
---------------------------------------------------------------
There aren't any plans to implement a Qpid JMS specific pooled connection
factory. There are already a few generic options that should work so there
isn't really a need to invent a new one.
One option is to use the PooledConnectionFactory provided by ActiveMQ which is
a JMS 1.1 based Connection pooling utility. It is tested with Camel already as
it is used to pool the ActiveMQ Connections. You can find the docs
[here|https://activemq.apache.org/maven/apidocs/org/apache/activemq/jms/pool/PooledConnectionFactory.html],
and the maven artifacts are
[here|https://mvnrepository.com/artifact/org.apache.activemq/activemq-pool/5.15.2].
Another option is [this|https://github.com/messaginghub/pooled-jms] JMS 2.0
aware Connection pool which you can use via the maven artifacts
[here|https://search.maven.org/#search%7Cga%7C1%7Ca%3A%22pooled-jms%22]. This
project has tests that use the Qpid JMS client library which you can use as a
reference for configuring it.
was (Author: tabish121):
There aren't any plans to implement a Qpid JMS specific pooled connection
factory. There are already a few generic options that should work so there
isn't really a need to invent a new one.
One option is to use the PooledConnectionFactory provided by ActiveMQ which is
a JMS 1.1 based Connection pooling utility. It is tested with Camel already as
it is used to pool the ActiveMQ Connections. You can find the docs
[here|https://activemq.apache.org/maven/apidocs/org/apache/activemq/jms/pool/PooledConnectionFactory.html],
and the maven artifacts are
[here|https://mvnrepository.com/artifact/org.apache.activemq/activemq-pool/5.15.2].
Another option is [this|https://github.com/messaginghub/pooled-jms] JMS 2.0
aware Connection pool which you can use via the maven artifacts
[here|https://search.maven.org/#search%7Cga%7C1%7Ca%3A%22pooled-jms%22].
> Add pooled connection factory
> -----------------------------
>
> Key: QPIDJMS-353
> URL: https://issues.apache.org/jira/browse/QPIDJMS-353
> Project: Qpid JMS
> Issue Type: Improvement
> Components: qpid-jms-client
> Affects Versions: 0.28.0
> Reporter: Nicola Ferraro
>
> A pooled connection factory was present in the amqp 0.x version of the
> library, but is missing in the current one.
> I've done some tests with Apache Camel (camel-amqp) and every message sent to
> a queue results into a new connection.
> A (always increasing) progressive number and a message about Sasl
> authentication is printed for every message. I suspect this is a waste of
> performance.
> Do you plan to add this feature?
> Relevant parts of the stack trace:
> {code}
> 10:13:03.161 [AmqpProvider :(3):[amqp://localhost:5672]] INFO
> o.a.q.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-PLAIN
> 10:13:03.201 [AmqpProvider :(3):[amqp://localhost:5672]] INFO
> org.apache.qpid.jms.JmsConnection - Connection
> ID:94d6f8bf-886f-46b2-8eff-af09f03dd46c:1 connected to remote Broker:
> amqp://localhost:5672
> 10:13:03.240 [AmqpProvider :(4):[amqp://localhost:5672]] INFO
> o.a.q.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-PLAIN
> 10:13:03.255 [AmqpProvider :(4):[amqp://localhost:5672]] INFO
> org.apache.qpid.jms.JmsConnection - Connection
> ID:946b64b6-dbc3-4ce7-b178-55de6759c26b:2 connected to remote Broker:
> amqp://localhost:5672
> 10:13:06.143 [AmqpProvider :(5):[amqp://localhost:5672]] INFO
> o.a.q.jms.sasl.SaslMechanismFinder - Best match for SASL auth was: SASL-PLAIN
> 10:13:06.181 [AmqpProvider :(5):[amqp://localhost:5672]] INFO
> org.apache.qpid.jms.JmsConnection - Connection
> ID:89593ca0-a185-4e51-80ef-bb6bf3dfbbbd:3 connected to remote Broker:
> amqp://localhost:5672
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
