Spring integration MessageChannelPartitionHandler使用来自QueueChannel的第一个可用回复，因此完成了错误的作业
我看到的问题与这里所说的相同 我有多个正在运行的作业，其中的步骤使用下面定义的相同父分区hanldler'parentPartitionHandler' 我所有的作业都有类似的配置，如下所示，第二步“studentPartitionAndProcessStep”是分区步骤Spring integration MessageChannelPartitionHandler使用来自QueueChannel的第一个可用回复，因此完成了错误的作业,spring-integration,Spring Integration,我看到的问题与这里所说的相同 我有多个正在运行的作业，其中的步骤使用下面定义的相同父分区hanldler'parentPartitionHandler' 我所有的作业都有类似的配置，如下所示，第二步“studentPartitionAndProcessStep”是分区步骤 <job id="studentLoadJob" xmlns="http://www.springframework.org/schema/batch" job-repository="jobReposito
<job id="studentLoadJob" xmlns="http://www.springframework.org/schema/batch"
job-repository="jobRepository" restartable="true" parent="abstractJob">
<step id="studentLoadStep" parent="parentLoadStep" next="studentPartitionAndProcessStep"/>
<step id="studentPartitionAndProcessStep" next="studentCleanupStep">
<partition partitioner="filePartitioner" handler="studentPartitionHandler"/>
</step>
<step id="studentCleanupStep" parent="parentCleanupStep"/>
</job>
<bean id="studentPartitionHandler"
parent="parentPartitionHandler">
<property name="stepName" value="studentPartitionStep"/>
</bean>
Message<Collection<StepExecution>> message = (Message<Collection<StepExecution>>) messagingGateway.receive(replyChannel);
<int:channel id="outboundRequests">
<int:dispatcher task-executor="taskExecutor" failover="true"/>
</int:channel>
<int:channel id="inboundStaging"/>
<int:channel id="inboundRequests"/>
<int:channel id="outboundStaging"/>
<int:channel id="setHeaderPartionHandlerReplyChannel"/>
<int-amqp:outbound-channel-adapter
id="filePartitionRequestOutboundGateway"
channel="outboundRequests"
amqp-template="rabbitTemplate"
exchange-name="${rabbitmq.classflow.exchange}"
routing-key="${rabbitmq.classflow.batch.partition.routingkey}"
mapped-request-headers="*"
/>
<int-amqp:inbound-channel-adapter
id="filePartitionRequestInboundGateway"
concurrent-consumers="${rabbitmq.classflow.batch.partition.consumers}"
channel="inboundRequests"
receive-timeout="60000000"
queue-names="${rabbitmq.classflow.batch.partition.queuename.request}"
connection-factory="rabbitConnectionFactory"
mapped-request-headers="*"
/>
<int:header-enricher input-channel="setHeaderPartionHandlerReplyChannel" output-channel="outboundRequests">
<int:header-channels-to-string/>
</int:header-enricher>
<int:service-activator ref="stepExecutionRequestHandler" input-channel="inboundRequests"
output-channel="outboundStaging"/>
<int-amqp:outbound-channel-adapter
id="filePartitionRepyOutboundGateway"
channel="outboundStaging"
amqp-template="rabbitTemplate"
exchange-name="${rabbitmq.classflow.exchange}"
routing-key="${rabbitmq.classflow.batch.partition.queuename.reply.routingkey}"
mapped-request-headers="*"
/>
<int-amqp:inbound-channel-adapter
id="filePartitionRepyInboundGateway"
channel="inboundStaging"
queue-names="${rabbitmq.classflow.batch.partition.queuename.reply}"
connection-factory="rabbitConnectionFactory"
concurrent-consumers="${rabbitmq.classflow.batch.tenant.job.consumers}"
mapped-request-headers="*"
/>
<int:aggregator ref="parentPartitionHandler"
send-partial-result-on-expiry="true"
send-timeout="60000000"
input-channel="inboundStaging"/>
<bean id="parentPartitionHandler"
class="org.springframework.batch.integration.partition.MessageChannelPartitionHandler">
<property name="gridSize" value="3"/>
<property name="messagingOperations">
<bean class="org.springframework.integration.core.MessagingTemplate">
<property name="defaultChannel" ref="setHeaderPartionHandlerReplyChannel"/>
<property name="receiveTimeout" value="60000000"/>
</bean>
</property>
<property name="stepName" value="parentPartitionStep"/>
</bean>
Mallikarjun这在Spring Batch 3.0.3中是固定的，只要不将特定的replyChannel注入分区处理程序 spring批处理集成现在是main的一部分 编辑 回应您上次关于使用适配器而不是网关的评论 是；网关负责保持replyChannel标头的完整性。使用适配器时需要一些额外的配置： 添加一个带有元素see的header enricher；这会将live header通道对象转换为通道注册表的键。 配置适配器以映射replyChannel标头，例如映射的请求标头=*。
网关不需要这样做，因为它在收到回复时保存了对出站消息的引用。我将spring batch版本从3.0.1更改为3.0.3。我在上面的帖子中注释掉了分区处理程序中的replyChanel引用。现在的问题是，分区处理程序会无限期地等待，并且不会返回在receivecurrentReplyChannel上。我验证了聚合器已处理组并将消息回复到outputChannel“outboundReplies”，但我从分区处理程序对此进行了评论。请不要
在注释中添加代码；无法阅读-请改为编辑您的问题。从聚合器中删除输出通道在您链接到的示例中没有输出通道，聚合器将自动将应答返回到分区处理程序中的内部应答通道。对不起，在上面发布的配置中，我使用的是带有输出通道的聚合器。是的，我引用的帖子没有使用它。我将从配置中删除输出通道并重试。您好，从聚合器AbstractMessageHandler中删除输出通道后，handleMessage不会抛出可用的outputChannel或replyChannel标头。。我是否需要添加replyChaneel作为标题的一部分？否；这意味着您不知何故丢失了内部回复通道——如果您使用的是Michael的配置，则不应发生这种情况；如果使用当前配置编辑问题，可能会更好。
Message<Collection<StepExecution>> message = (Message<Collection<StepExecution>>) messagingGateway.receive(replyChannel);
<int:channel id="outboundRequests">
<int:dispatcher task-executor="taskExecutor" failover="true"/>
</int:channel>
<int:channel id="inboundStaging"/>
<int:channel id="inboundRequests"/>
<int:channel id="outboundStaging"/>
<int:channel id="setHeaderPartionHandlerReplyChannel"/>
<int-amqp:outbound-channel-adapter
id="filePartitionRequestOutboundGateway"
channel="outboundRequests"
amqp-template="rabbitTemplate"
exchange-name="${rabbitmq.classflow.exchange}"
routing-key="${rabbitmq.classflow.batch.partition.routingkey}"
mapped-request-headers="*"
/>
<int-amqp:inbound-channel-adapter
id="filePartitionRequestInboundGateway"
concurrent-consumers="${rabbitmq.classflow.batch.partition.consumers}"
channel="inboundRequests"
receive-timeout="60000000"
queue-names="${rabbitmq.classflow.batch.partition.queuename.request}"
connection-factory="rabbitConnectionFactory"
mapped-request-headers="*"
/>
<int:header-enricher input-channel="setHeaderPartionHandlerReplyChannel" output-channel="outboundRequests">
<int:header-channels-to-string/>
</int:header-enricher>
<int:service-activator ref="stepExecutionRequestHandler" input-channel="inboundRequests"
output-channel="outboundStaging"/>
<int-amqp:outbound-channel-adapter
id="filePartitionRepyOutboundGateway"
channel="outboundStaging"
amqp-template="rabbitTemplate"
exchange-name="${rabbitmq.classflow.exchange}"
routing-key="${rabbitmq.classflow.batch.partition.queuename.reply.routingkey}"
mapped-request-headers="*"
/>
<int-amqp:inbound-channel-adapter
id="filePartitionRepyInboundGateway"
channel="inboundStaging"
queue-names="${rabbitmq.classflow.batch.partition.queuename.reply}"
connection-factory="rabbitConnectionFactory"
concurrent-consumers="${rabbitmq.classflow.batch.tenant.job.consumers}"
mapped-request-headers="*"
/>
<int:aggregator ref="parentPartitionHandler"
send-partial-result-on-expiry="true"
send-timeout="60000000"
input-channel="inboundStaging"/>
<bean id="parentPartitionHandler"
class="org.springframework.batch.integration.partition.MessageChannelPartitionHandler">
<property name="gridSize" value="3"/>
<property name="messagingOperations">
<bean class="org.springframework.integration.core.MessagingTemplate">
<property name="defaultChannel" ref="setHeaderPartionHandlerReplyChannel"/>
<property name="receiveTimeout" value="60000000"/>
</bean>
</property>
<property name="stepName" value="parentPartitionStep"/>
</bean>