My enterprise application is divided into modules connected over JMS. First module acts as a dispatcher - it receives request from remote clients, does some request processing and forwards message to the JMS topic.
Also, there are multiple other modules which are registered in topic. Every time message comes, it should be forwarded to all of these modules (consumers). Only one consumer is able to process one kind of messages - each one is doing some detection. If module detects that it should handle this kind of message, it does so, and replies to dispatcher. If, however, consumer will find out that it is not responsible to handle this kind of message, it sends processing to the nullChannel.
Whole integration is based on SI components:
Dispatcher [jms:outbound-gateway] - HORNETQ TOPIC - [jms:inbound-gateway] Consumer (multiple instances)
Below is the typical use case (1 dispatcher, 2 consumers):
1. remote client sends request to the dispatcher
2. dispatcher does some processing on the message, and forwards it to JMS topic
3a. first instance of consumer analyzes message content, and it found appropriate handler - it starts processing. When it will be finished, consumer replies to dispatcher with processed message
3b. (at the same time when first consumer process message) second instance of consumer analyzes message content, and it cannot find an appropriate handler. It drops message by sending it to SI nullChannel.
Lets assume that this scenario is reapeated e.g. 100 times - every time only first consumer can handle this type of message.
Because consumer code is very fast, first consumer process every of these messages, and every time sends response to the dispatcher.
Second consumer should 100 times drop message.
The problem is:
Messages comes to the first consumer from HornetQ very fast.
Messages comes to the second consumer from HornetQ very slow.
It is not the case that 2nd consumer is slow - I sniffed network link, and it looks like hornetq broker slows down messages delivering frequence to the second consumer
This leads to the situation, that the first consumer has already processed all messages and send them back to dispatcher, and at the same time second consumer still receives delayed messages (client has already processed response).
Is it possible that this situation is caused by sending JMS messages to the nullChannel? I've done integration testing before (using ActiveMQ broker), and then, consumers has been receiving messages simulatenously. Now, with HornetQ first consumer receives them really fast, second - really slow.
Below is part of my configuration (consumer / producer):
<beans:property name="targetConnectionFactory" ref="targetConnectionFactory" />
<beans:property name="sessionCacheSize" value="10" />
<beans:property name="cacheProducers" value="false" />
<beans:bean id="targetConnectionFactory" class="org.hornetq.jms.client.HornetQConnectionFactory">
<beans:map key-type="java.lang.String" value-type="java.lang.Object">
<beans:entry key="host" value="localhost" />
<beans:entry key="port" value="5445" />
<beans:property name="clientID" value="AnossstherConsumer"/> <!-- different for every consumer -->
<beans:bean name="requestTopic" class="org.hornetq.api.jms.HornetQJMSClient" factory-method="createTopic">
<beans:constructor-arg index="0" value="TopicRequestDemo"/>
<beans:bean name="responseTopic" class="org.hornetq.api.jms.HornetQJMSClient" factory-method="createTopic">
<beans:constructor-arg index="0" value="TopicResponseDemo"/>
HornetQ configuration in hornetq-jms.xml:
Thanks for any advices!