CODEWITHSUNDEEP
spring-integrationspring-batchspring-jms
Mike Rother
Mike Rother

Reputation: 639

Spring Batch Partitioned Job Using Durable Subscriber

We are using Spring Batch and partitioning of jobs in a 10 server JBoss EAP 5.2 cluster. Because of a problem in JBoss messaging, we needed to use a topic for the reply message from the partitioned steps. All has been working fine until we see JBoss Messaging glitches (on the server that launches the job) and that drops it from the cluster. It recovers but the main partition does no``t pick up the messages sent from the partition steps. I see the messages in the topic in the JMX-Console but also see that the subscription and the messages are non-durable. Therefore I would like to make the communication for the partition step reply into a durable subscription. I can't seem to fine a document way to do this. This is my current configuration of the partitioned step and associated bean.

Inbound Gateway Configuration

<int:channel id="springbatch.slave.jms.request"/>
<int:channel id="springbatch.slave.jms.response" />

<int-jms:inbound-gateway 
    id="springbatch.master.inbound.gateway" 
    connection-factory="springbatch.listener.jmsConnectionFactory" 
    request-channel="springbatch.slave.jms.request" 
    request-destination="springbatch.partition.jms.requestsQueue" 
    reply-channel="springbatch.slave.jms.response" 
    concurrent-consumers="${springbatch.partition.concurrent.consumers}" 
    max-concurrent-consumers="${springbatch.partition.concurrent.maxconsumers}"
    max-messages-per-task="${springbatch.partition.concurrent.maxmessagespertask}"
    reply-time-to-live="${springbatch.partition.reply.time.to.live}"
    />

Outbound Gateway Configuration

<int:channel id="jms.requests">
    <int:dispatcher task-executor="springbatch.partitioned.jms.taskExecutor" />
</int:channel>
<int:channel id="jms.reply" />

<int-jms:outbound-gateway id="outbound-gateway"
    auto-startup="false" connection-factory="springbatch.jmsConnectionFactory"
    request-channel="jms.requests"
    request-destination="springbatch.partition.jms.requestsQueue"
    reply-channel="jms.reply"
    reply-destination="springbatch.partition.jms.repliesQueue"
    correlation-key="JMSCorrelationID">
    <int-jms:reply-listener />
</int-jms:outbound-gateway>

</code>

Upvotes: 2

Views: 207

Answers (1)

Gary Russell
Gary Russell

Reputation: 174564

Further to Michael's comment; there is currently no way to configure a topic for the <reply-listener/> - it's rather unusual to use a topic in a request/reply scenario and we didn't anticipate that requirement.

Feel free to open a JIRA Issue against Spring Integration.

An alternative would be to wire in an outbound-channel-adapter for the requests and an inbound-channel-adapter for the replies. However, some special handling of the replyChannel header is needed when doing that - see the docs here for more information about that.

Upvotes: 1

Related Questions