Hello.

Yes, I use PAX JMS, installing it with this feature (adding the ActiveMQ 5.17.3 repository and PAX dependencies) :

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<features xmlns="http://karaf.apache.org/xmlns/features/v1.6.0"; name="${project.artifactId}">
<repository>mvn:org.apache.activemq/activemq-karaf/${version.of.activemq}/xml/features</repository>
    <feature name="${project.artifactId}" version="${project.version}">
        <feature prerequisite="true" version="${version.of.activemq}">activemq-client</feature>
        <feature prerequisite="true">pax-jms-activemq</feature>
        <feature prerequisite="true">pax-jms-pool-pooledjms</feature>
        <feature prerequisite="true">pax-jms-config</feature>
    </feature>
</features>

And with this configuration file :

type=activemq
connectionFactoryType=ConnectionFactory
name=alice-jms
osgi.jndi.service.name=jms/test
jms.url=tcp://localhost:6000
jms.user=application
jms.password=secret
jms.clientIDPrefix=CATERPILLAR
xa=false
pool=pooledjms
pool.maxConnections=256

I don't think this come from the ActiveMQ client (not server) : I used the same before with a connection factory created by a blueprint, with more 2 millions messages sent/received in tests with the same Camel routes, and after several days running.

Now the warning messages come after seconds or minutes, as if the pool was altered by some cleaning operation on live connections.

I also use PAX JDBC, that works perfectly :) !

Thanks.

Regards.

Ephemeris Lappis

Le 14/02/2023 à 06:58, Jean-Baptiste Onofré a écrit :
Are you using camel-jms ? What's the camel endpoint URI ?

Regards
JB

On Mon, Feb 13, 2023 at 7:17 PM Ephemeris Lappis
<[email protected]> wrote:
Hello.

I've changed a handmade JMS Connection factory to use PAX JMS with pooling.
Now I've strange warning messages that come after some time :

DefaultJmsMessageListenerContainer | 209 -
org.apache.servicemix.bundles.spring-jms - 5.3.23.1 |  | Setup of JMS
message listener invoker failed for destination
'bbbmmm999-f902.internal.queue' - trying to recover. Cause: The
Consumer is closed

Each time, I have a message for every Camel route consumer.

Is it a configuration issue on PAX JMS ? For now I've not set any
parameters about idle time and so on : only maximum connections...

pool=pooledjms
pool.maxConnections=256

Thanks for your help.

Thanks.

--
Cet e-mail a été vérifié par le logiciel antivirus d'Avast.
www.avast.com

Reply via email to