CODEWITHSUNDEEP
jmsapache-camelsolace-mqsolace
Lewis Wong
Lewis Wong

Reputation: 269

Solace JMS didn't run with parallel threads in Camel

In order to perform parallel processing of jms messages, I have configured the JmsComponent and connectionFactory as below.

After reading some posts and the official tutorial, seems that the below configuration should work for ActiveMQ. However, my testing shows that it doesn't work on Solace. Can someone give me a hint on this? Thanks.

// Route Definition - Camel Java DSL from(INBOUND_ENDPOINT).setExchangePattern(ExchangePattern.InOnly).threads(5).bean(ThroughputMeasurer.class);

<!-- JMS Config -->
<bean id="jms" class="org.apache.camel.component.jms.JmsComponent">
    <property name="connectionFactory" ref="cachedConnectionFactory" />
    <property name="acknowledgementModeName" value="AUTO_ACKNOWLEDGE" />
    <property name="deliveryPersistent" value="false" />
    <property name="asyncConsumer" value="true" />
    <property name="concurrentConsumers" value="5" />
</bean>

<!-- jndiTemplate is omitted here -->

<bean id="connectionFactory" class="org.springframework.jndi.JndiObjectFactoryBean">
    <property name="jndiTemplate" ref="jndiTemplate" />
    <property name="jndiName" value="ceConnectionFactory" />
</bean>

<bean id="cachedConnectionFactory"
    class="org.springframework.jms.connection.CachingConnectionFactory">
    <property name="targetConnectionFactory" ref="connectionFactory" />
    <property name="sessionCacheSize" value="30" />
</bean>

Upvotes: 0

Views: 1670

Answers (2)

Russell Sim
Russell Sim

Reputation: 1733

I believe the problem here is that your consumer is bound to an exclusive queue, and only 1 consumer is allowed to process message. Binding to an non-exclusive queue should solve the problem.

Exclusive queues only allow the first consumer to consume from the queue. All other consumers that are bound to the queue will not receive data. In the event that the first consumer disconnects, the next oldest consumer will begin receiving data. The other consumers can be thought of as being "standby" consumers that will take over the moment the first consumer disconnects.

Non-exclusive queues are used for load balancing. Messages that are spooled to the queue will be distributed to all consumers in a round-robin manner.

Upvotes: 1

Peter Keller
Peter Keller

Reputation: 7636

Check:

  • Are there any exception messages in the log?
  • Is the jndiName correct? Perhaps it should be jms/ceConnectionFactory?
  • Is the URI INBOUND_ENDPOINT correct?
  • ...

Try to setup ActiveMQ first, and migrate the configuration to Solace.

Upvotes: 0

Related Questions