I'm testing with Tomcat 8.5.23 with addition of:
rabbitmq-jms-1.8.1.jar
geronimo-jms_1.1_spec-1.1.1.jar
amqp-client-4.3.0.jar
slf4j-api-1.6.1.jar
Settings in server.properties:
Code:
messaging.dispatcherImplementer: com.isomorphic.messaging.JMSMessageDispatcher messaging.jms.context: _container_ messaging.jms.jndiPrefix: jms messaging.jms.topicConnectionFactory: ConnectionFactory messaging.jms.encoding: json
Code:
<Resource name="jms/ConnectionFactory" type="javax.jms.ConnectionFactory" factory="com.rabbitmq.jms.admin.RMQObjectFactory" username="xyz" password="xyz" virtualHost="/" host="myHost" threadsPerConnection="2" cleanUpServerNamedQueuesForNonDurableTopicsOnSessionClose="true" />
Code:
<Resource auth="Container" name="jms/updateMappaJtaChannel" type="javax.jms.Topic" factory="com.rabbitmq.jms.admin.RMQObjectFactory" destinationName="updateMappaJtaChannel" /> <ResourceLink global="jms/updateMappaJtaChannel" name="jms/updateMappaJtaChannel"/> <ResourceLink global="jms/ConnectionFactory" name="jms/ConnectionFactory" type="javax.jms.ConnectionFactory"/>
But then there's another issue.
Actually I've got the same exact behaviour without the updateMappaJtaChannel resource definition, so it is ignored.
This is in agreement with what I wrote previously in this thread, where I said that I was trying the amqp settings in the queue configuration, otherwise, as I wrote in post #34:
Originally posted by claudiobosticco
View Post
Code:
<Resource auth="Container" name="jms/updateMappaJtaChannel" type="javax.jms.Topic" factory="com.rabbitmq.jms.admin.RMQObjectFactory" destinationName="updateMappaJtaChannel" amqp="true" amqpExchangeName="jms.durable.topic" amqpRoutingKey="updateMappaJtaChannel" amqpQueueName="updateMappaJtaChannel" />
Leave a comment: