I want to use a executor-channel instead of an direct-channel, but I face an issue I don`t understand.
Working Config:
<int:channel id="newByteArrayChannel" datatype="java.lang.Byte[]" />
<int:service-activator
id="myEncryptionServiceActivator"
ref="encryptionServiceConnector"
method="encrypt"
input-channel="newByteArrayChannel"
output-channel="encryptedByteArrayChannel"
requires-reply="true"
send-timeout="1000"
/>
Changed to (Not Working):
<int:channel id="newByteArrayChannel" datatype="java.lang.Byte[]">
<int:dispatcher task-executor="myExecutor" />
</int:channel>
<task:executor id="myExecutor" pool-size="4" queue-capacity="10" keep-alive="10000"/>
<int:service-activator
id="myEncryptionServiceActivator"
ref="myServiceConnector"
method="encrypt"
input-channel="newByteArrayChannel"
output-channel="encryptedByteArrayChannel"
requires-reply="true"
send-timeout="1000"
/>
Error:
Exception in thread "main" org.springframework.messaging.MessageDeliveryException: Channel 'newByteArrayChannel' expected one of the following datataypes [class [Ljava.lang.Byte;], but received [class [B]
Thanks in advance :-)
It's a bug - I opened a JIRA Issue.
As a work-around, you could bridge a direct channel to the executor channel, or change newByteArrayChannel to a publish subscribe channel - (with only one subscriber, or course).
<int:publish-subscribe-channel id="newByteArrayChannel"
datatype="java.lang.Byte[]" task-executor="myExecutor" />
Or you can explicitly inject a DefaultDatatypeChannelMessageConverter bean into the channel.
As well Gery Russels solution works, I ended up with a different solution I also wants to share. I did the incoming channel as queue channel, and poll it from the service-activator using a task-executor:
<int:channel id="newByteArrayChannel" datatype="java.lang.Byte[]">
<int:queue capacity="1000"/>
</int:channel>
<int:service-activator
id="myEncryptionServiceActivator"
ref="myServiceConnector"
method="encrypt"
input-channel="newByteArrayChannel"
output-channel="encryptedByteArrayChannel"
requires-reply="true"
send-timeout="1000"
>
<int:poller fixed-delay="100" task-executor="myExecutor"/>
</int:service-activator>
<task:executor id="myExecutor" pool-size="4-32" queue-capacity="10000" keep-alive="10000"/>
Related
I would like to get the message from JMS and send it as HTTP request and in case of failure, enqueue it again to JMS.
I've tried using inbound-message-adapter and message-driven-channel-adapter, but it fails as I get "ChannelResolutionException: no output-channel or replyChannel header available" exception but since I do not want to reply to inbound-message-adapter, not sure why would I include a replyChannel header
<jms:outbound-channel-adapter id="outboundJMSAdaptor" jms-template="jmsTemplate"
channel="jmsOutChannel"
destination="requestQueue"/>
<int:channel id="jmsInChannel" />
<jms:message-driven-channel-adapter
channel="jmsInChannel" destination="requestQueue"
connection-factory="jmsConnectionFactory" message-converter="jmsMessageConverter"/>
<int:header-enricher input-channel="jmsInChannel" output-channel="header_enriched_request">
<int:header name="addressId" expression="payload.getId()"/>
<int:header name="Accept-Language" value="en_GB"/>
<int:header name="X-Source-CountryCode" value="GB"/>
<int:header name="X-Source-Operator" value="Enterprise"/>
<int:header name="X-Source-Division" value="CustomerManagement"/>
<int:header name="X-Source-System" value="${sapwebservices.http.header.source.system}"/>
<int:header name="X-Source-Timestamp" expression="new java.text.SimpleDateFormat('yyyy-MM-dd HH:mm:ss').format(new java.util.Date())"/>
<int:header name="Accept" value="application/json"/>
<int:header name="Content-Type" value="application/json;charset=UTF-8"/>
</int:header-enricher>
<int:object-to-json-transformer input-channel="header_enriched_request"
output-channel="update_customer_shipping_address_outbound_gateway"
object-mapper="nonNullObjectMapper"/>
<http:outbound-gateway mapped-request-headers="Accept*, Content-Type, X-*, HTTP_REQUEST_HEADERS"
request-channel="update_customer_shipping_address_outbound_gateway"
reply-channel="print_payload_update_shipping"
url="${sapwebservices.ws.uri.updatecustomershippingaddress}"
http-method="PUT"
expected-response-type="java.lang.String"
charset="UTF-8"
request-factory="updateCustomerAccountRequestFactory">
<http:uri-variable name="id" expression="headers['addressId']"/>
</http:outbound-gateway>
<int:service-activator input-channel="print_payload_update_shipping" output-channel="clean_no_print_char_update_customershippingaddress" ref="sapPrintPayload"/>
<int:transformer input-channel="clean_no_print_char_update_customershippingaddress" output-channel="resp_mapping_json_to_jsonobj_updatecustomershippingaddress">
<bean class="util.CleanNoPrintCharTransformer"/>
</int:transformer>
<int:json-to-object-transformer input-channel="resp_mapping_json_to_jsonobj_updatecustomershippingaddress"
output-channel="clean_no_print_char_update_customershippingaddress"
type="customer_shipping_address_response.json.CustomerShippingAddressResponse"/>
<int:transformer input-channel="clean_no_print_char_update_customershippingaddress" output-channel="">
<bean class="transformer.CreateCustomerShippingAddressPostTransformer"/>
</int:transformer>
I expect a success in a normal run, getting error
org.springframework.integration.dispatcher.AggregateMessageDeliveryException: All attempts to deliver Message to MessageHandlers failed. Multiple causes:
All attempts to deliver Message to MessageHandlers failed. Multiple causes:
no output-channel or replyChannel header available
org.springframework.integration.MessageHandlingException: org.springframework.expression.spel.SpelEvaluationException: EL1004E:(pos 8): Method call: Method transform(rest.bbr.customer_shipping_address_response.json.CustomerShippingAddressResponse) cannot be found on bbr.sap.util.CleanNoPrintCharTransformer type
See below for the stacktrace of the first cause.
org.springframework.integration.MessageHandlingException: org.springframework.expression.spel.SpelEvaluationException: EL1004E:(pos 8): Method call: Method transform(java.lang.String) cannot be found on bbr.sap.transformer.CreateCustomerShippingAddressPostTransformer type
See below for the stacktrace of the first cause.
Also, would like to enqueue the message again to the jms queue if the http:outbound-gateway respond as null or if the 3rd party services are down.
<int:transformer input-channel="clean_no_print_char_update_customershippingaddress"
output-channel="">
You can't have an empty output channel on a transformer.
It doesn't really make sense to transform something and then just discard the transformed result but if that's what you really want to do, send it to the nullChannel
<int:transformer input-channel="clean_no_print_char_update_customershippingaddress"
output-channel="nullChannel">
Scenario could be: my expectation could be 10 datapoint in batch, and I want to give response for {failed 5, pass 5} or sth.
my logic is to split the batch into data element and do validation.
successful validation will send to aggreagtor,
failed validation will throw error and pick up by error channel.
recipient-list-router take the errorChannel as inputChannel and 2 filter connect to it, the purpose is to filter some type of error to send response directly(eception unrelated to user input - server error or etc) and some type of client side error will go to aggregator to build response.
Is any problem with the logic?
My problem is I keep getting "Reply message received but the receiving thread has already received a reply" when build up the Result using service-activator after aggregator. this service-activator connect to replyChannel and it seems like there are some message already sent to this channel?
I checked my integration work flow only this service-activator and server error branch after "error filter" connect to replyChannel(but the handle is never called.)
Something wrong? BTW, can recipient-list-router or other type of endpoint connect to errorChannel? or it has to be service-activator as what I saw in all the example online?(but they are really simple example..)
Sample XML
<int:gateway id="myGateway" service-interface="someGateway" default-request-channel="splitChannel" error-channel="errorChannel" default-reply-channel="replyChannel" async-executor="MyThreadPoolTaskExecutor"/>
<int:splitter input-channel="splitChannel" output-channel="transformChannel" method="split">
<bean class="Splitter" />
</int:splitter>
<int:transformer id="transformer" input-channel="transformChannel" method="transform" output-channel="aggregateChannel">
<bean class="Transformer"/> // this may throw the validation error (filter_ErrorType_1), if it cannot transform
</int:transformer>
<int:aggregator id="aggregator"
input-channel="aggregateChannel"
output-channel="createAnswerChannel"
method="aggregate">
<bean class="MyAggregator" />
</int:aggregator>
<int:recipient-list-router id="myErrorRouter" input-channel="errorChannel">
<int:recipient channel="filter_ErrorType_1"/>
<int:recipient channel="filter_ErrorType_2"/>
<int:recipient channel="filter_ErrorType_3"/>
</int:recipient-list-router>
<int:filter input-channel="filter_ErrorType_1" output-channel="aggregateChannel" method="accept"></int:filter>
<int:filter input-channel="filter_ErrorType_2" output-channel="createErrorAnswerChannel" method="accept"></int:filter>
<int:filter input-channel="filter_ErrorType_3" output-channel="createErrorAnswerChannel" method="accept"></int:filter>
<int:service-activator input-channel='createErrorAnswerChannel' output-channel="replyChannel" method='buildError'>
<bean class="AnswerBuilder"/>
</int:service-activator>
<int:service-activator input-channel='createAnswerChannel' output-channel="replyChannel" method='build'>
<bean class="AnswerBuilder"/>
</int:service-activator>
Follow up:
<int:gateway id="myGateway" service-interface="someGateway" default-request-channel="splitChannel" error-channel="errorChannel" default-reply-channel="replyChannel" async-executor="MyThreadPoolTaskExecutor"/>
<int:splitter input-channel="splitChannel" output-channel="transformChannel" method="split">
<bean class="Splitter" />
</int:splitter>
<int:transformer id="transformer1" input-channel="toTransformer1" method="transform" output-channel="toTransformer2">
<bean class="Transformer1"/> // this may throw the validation error (filter_ErrorType_1), if it cannot transform
</int:transformer>
<int:transformer id="transformer2" input-channel="toTransformer2" method="transform" output-channel="toTransformer3">
<bean class="Transformer2"/> // this may throw the validation error (filter_ErrorType_2), if it cannot transform
</int:transformer>
<int:transformer id="transformer3" input-channel="toTransformer3" method="transform" output-channel="aggregateChannel">
<bean class="Transformer3"/> // this may throw the validation error (filter_ErrorType_3), if it cannot transform
</int:transformer>
???
// seems like you are proposing to have one gateway for each endpoint that may throw error.
// but in this case, take transfomer 1 for example, I cannot output the gateway directly to aggregate channel since for valid data it has to go to transformer 2
// but the failed message throwed by the error handler cannot pass transformer 2 because of afterall this is a error message not a valid data for transformer 2
// <int:service-activator input-channel="toTransformer1" output-channel="toTransformer2" ref="gateway1"/>
// <int:gateway id="gateway1" default-request-channel="toTransformer1" error-channel="errorChannel1"/>
// <int:transformer id="transformer" input-channel="toTransformer1" method="transform">
// <bean class="Transformer"/> // this may throw the validation error (filter_ErrorType_1), if it cannot transform
// </int:transformer>
// how to deal with this problem?
<int:service-activator input-channel='createErrorAnswerChannel' output-channel="replyChannel" method='buildError'>
<bean class="AnswerBuilder"/>
</int:service-activator>
<int:service-activator input-channel='createAnswerChannel' output-channel="replyChannel" method='build'>
<bean class="AnswerBuilder"/>
</int:service-activator>
I actually have complicated logic inside but I use transformer 123 to represent here.
Your question isn't clear. Please,be sure in the future provide more concrete info. Some config and StackTrace or logs are useful, too.
I guess that you have in the beginning of your flow <gateway> with configured error-channel. That's why you are receiving Reply message received but the receiving thread has already received a reply.
But I can't be sure, because there is no those words in your question. Right?
You can't rely on the errorChannel header there and come back for the reply eventually because the errorChannel header in case of Gateway is the same as replyChannel, and it is TemporaryReplyChannel - one-shot-usage channel and only for receive() operation.
Since we don't have any configuration or code from you we can't help you properly.
I suppose you need a middle-flow gateway via service-activator:
<service-activator id="gatewayTestService" input-channel="inputChannel"
output-channel="outputChannel" ref="gateway"/>
<gateway id="gateway" default-request-channel="requestChannel" error-channel="myErrorChannel"/>
or <chain> with <gateway> to perform validation and catch errors only there and return a desired reply for failures. That service-activator will be able to send them all to the <aggregator> afterward. In this case the <aggregator> can reply back to the gateway properly.
EDIT
errorChannel is a name for default global bean to catch any error messages from any Integration place. See more info in the http://docs.spring.io/spring-integration/reference/html/configuration.html#namespace-errorhandler.
So, that name is fully bad for your use case , because that myErrorRouter is going to handle ALL the errors!
The <int:recipient-list-router> sends message to all its recipients if it passes a selector or if there is no selector.
You don't need default-reply-channel on the <gateway> if it isn't publish-subscribe. You can just rely on the replyChannel header, which works if there is no output-channel defined.
What I'm talking about <service-activator> and <gateway> is pretty straight forward in front of your <transformer> after <splitter>:
<int:service-activator input-channel="transformChannel"
output-channel="aggregateChannel" ref="gateway"/>
<int:gateway id="gateway" default-request-channel="transformChannel" error-channel="validationErrorChannel"/>
<int:transformer id="transformer" input-channel="transformChannel" method="transform">
<bean class="Transformer"/> // this may throw the validation error (filter_ErrorType_1), if it cannot transform
</int:transformer>
So, splitter sends items to the service-activator. That one proceeds with the message to the gateway around transformer with custom error-channel exactly for one item. The transformer answers to the replyChannel exactly to that previous gateway. If it throws some Exception, it is handled by the validationErrorChannel process. Which should reply with some compensation message. That message is bubbled to the service-activator. Finally service-activator sends a result to the aggregateChannel. And it is black box for the service-activator if validation was good or not.
Hope that helps a bit.
EDIT2
I'm disappointed that you haven't accepted my advises in your code, but nevertheless that is how I see it:
<int:gateway id="myGateway" service-interface="someGateway" default-request-channel="splitChannel"
async-executor="MyThreadPoolTaskExecutor" />
<int:splitter input-channel="splitChannel" output-channel="transformChannel" method="split">
<bean class="Splitter" />
</int:splitter>
<int:service-activator input-channel="validateChannel" output-channel="aggregateChannel"
ref="validateGateway"/>
<gateway id="validateGateway" default-request-channel="toTransformer1" error-channel="myErrorChannel"/>
<chain input-channel="toTransformer1">
<int:transformer method="transform">
<bean class="Transformer1" />
</int:transformer>
<int:transformer method="transform">
<bean class="Transformer2" />
</int:transformer>
<int:transformer method="transform">
<bean class="Transformer3" />
</int:transformer>
</chain>
<int:service-activator input-channel="myErrorChannel" method="buildError">
<bean class="AnswerBuilder" />
</int:service-activator>
<int:aggregator id="aggregator"
input-channel="aggregateChannel"
output-channel="createAnswerChannel"
method="aggregate">
<bean class="MyAggregator" />
</int:aggregator>
<int:service-activator input-channel='createAnswerChannel' method='build'>
<bean class="AnswerBuilder" />
</int:service-activator>
Pay attention, how I chain transformers. So, you have one gateway for all your transformers and any error on any of them will be thrown to the gateway for error handling on the myErrorChannel.
I am using Spring Integration to send notifications and as an error test case, I am sending in malformed JSON (a Map) and am getting MessagingException which seems to just go on and on.. not stopping.. I have to kill the Application.
So want to know how to capture this, may be via errorChannel. Code examples would be helpful.
My Spring Integration config:
<!-- channel to connect to disruption exchange -->
<int-amqp:publish-subscribe-channel id="inputChannel"
connection-factory="connectionFactory"
exchange="notification.exchange"/>
<int:json-to-object-transformer input-channel="inputChannel"
output-channel="notificationChannel"
type="java.util.Map"/>
<int:channel id="notificationChannel">
<int:interceptors>
<int:wire-tap channel="loggingChannel"/>
</int:interceptors>
</int:channel>
<int:logging-channel-adapter id="loggingChannel" log-full-message="true" logger-name="tapInbound" level="INFO"/>
<!-- depending on the deviceType route to either apnsChannel or gcmChannel -->
<int:router ref="notificationTypeRouter" input-channel="notificationChannel"/>
<!-- apple push notification channel-->
<int:channel id="apnsChannel"/>
<!-- service activator to process disruptionNotificationChannel -->
<int:service-activator input-channel="apnsChannel" ref="apnsPushNotificationService" method="pushNotification"/>
<!-- google cloud messaging notification channel-->
<int:channel id="gcmChannel"/>
<!-- service activator to process disruptionNotificationChannel -->
<int:service-activator input-channel="gcmChannel" ref="gcmPushNotificationService" method="pushNotification"/>
<!-- error channel to may be log to file or email or store to db in the future -->
<int:channel id="errorChannel"/>
<int:service-activator input-channel="errorChannel" ref="notificationErrorHandler" method="handleFailedNotification"/>
<!-- Infrastructure -->
<rabbit:connection-factory id="connectionFactory"
host="${spring.rabbitmq.host}"
port="${spring.rabbitmq.port}"
username="${spring.rabbitmq.username}"
password="${spring.rabbitmq.password}"/>
<rabbit:template id="amqpTemplate" connection-factory="connectionFactory"/>
<rabbit:admin connection-factory="connectionFactory"/>
<rabbit:fanout-exchange name="notification.exchange"/>
I also have an error handler:
public class NotificationErrorHandler {
private final Logger LOG = LoggerFactory.getLogger(NotificationErrorHandler.class);
public void handleFailedNotification(Message<MessageHandlingException> message) {
Map<String, Object> map = (Map) message.getPayload();
Notification notification = Notification.fromMap(map);
saveToBD(notification);
}
private void saveToBD(Notification notification) {
LOG.error("[Notification-Error-Handler] Couldn't Send Push notification: device='{}', type='{}', pushId='{}', message='{}', uid='{}'",
new Object[]{notification.getDevice(),
notification.getDeviceType(),
notification.getDeviceToken(),
notification.getBody(),
notification.getUid()});
}
}
This is the exception:
Caused by: org.springframework.messaging.MessagingException: Failure occured in AMQP listener while attempting to convert and dispatch Message.; nested exception is org.springframework.integration.transformer.MessageTransformationException: failed to transform message; nested exception is com.fasterxml.jackson.core.JsonParseException: Unexpected character ('}' (code 125)): was expecting double-quote to start field name
at [Source: [B#7a707c2c; line: 7, column: 2]
at org.springframework.integration.amqp.channel.AbstractSubscribableAmqpChannel$DispatchingMessageListener.onMessage(AbstractSubscribableAmqpChannel.java:202)
at org.springframework.amqp.rabbit.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:799)
... 10 common frames omitted
Caused by: org.springframework.integration.transformer.MessageTransformationException: failed to transform message; nested exception is com.fasterxml.jackson.core.JsonParseException: Unexpected character ('}' (code 125)): was expecting double-quote to start field name
at [Source: [B#7a707c2c; line: 7, column: 2]
at org.springframework.integration.transformer.AbstractTransformer.transform(AbstractTransformer.java:44)
at org.springframework.integration.transformer.MessageTransformingHandler.handleRequestMessage(MessageTransformingHandler.java:68)
at org.springframework.integration.handler.AbstractReplyProducingMessageHandler.handleMessageInternal(AbstractReplyProducingMessageHandler.java:99)
at org.springframework.integration.handler.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:78)
at org.springframework.integration.dispatcher.BroadcastingDispatcher.invokeHandler(BroadcastingDispatcher.java:160)
at org.springframework.integration.dispatcher.BroadcastingDispatcher.dispatch(BroadcastingDispatcher.java:142)
at org.springframework.integration.amqp.channel.AbstractSubscribableAmqpChannel$DispatchingMessageListener.onMessage(AbstractSubscribableAmqpChannel.java:181)
... 11 common frames omitted
Caused by: com.fasterxml.jackson.core.JsonParseException: Unexpected character ('}' (code 125)): was expecting double-quote to start field name
at [Source: [B#7a707c2c; line: 7, column: 2]
at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1419)
at com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:508)
at com.fasterxml.jackson.core.base.ParserMinimalBase._reportUnexpectedChar(ParserMinimalBase.java:437)
Hope someone can help.
Thanks in advance
GM
Changes made as per #Gary's answer and its working now:
<!-- Infrastructure -->
<rabbit:connection-factory id="connectionFactory"
host="${spring.rabbitmq.host}"
port="${spring.rabbitmq.port}"
username="${spring.rabbitmq.username}"
password="${spring.rabbitmq.password}"/>
<rabbit:admin connection-factory="connectionFactory"/>
<rabbit:template id="amqpTemplate" connection-factory="connectionFactory"/>
<rabbit:direct-exchange name="notification.direct">
<rabbit:bindings>
<rabbit:binding queue="notification.queue" key="notification.queue"/>
</rabbit:bindings>
</rabbit:direct-exchange>
<rabbit:queue id="notification.queue" name="notification.queue"/>
<int-amqp:inbound-channel-adapter channel="inputChannel"
queue-names="notification.queue"
connection-factory="connectionFactory"
error-channel="errorChannel"/>
<int:json-to-object-transformer input-channel="inputChannel"
output-channel="notificationChannel"
type="java.util.Map"/>
<int:channel id="notificationChannel">
<int:interceptors>
<int:wire-tap channel="loggingChannel"/>
</int:interceptors>
</int:channel>
<int:logging-channel-adapter id="loggingChannel" log-full-message="true" logger-name="tapInbound" level="INFO"/>
<!-- depending on the deviceType route to either apnsChannel or gcmChannel -->
<int:router ref="notificationTypeRouter" input-channel="notificationChannel"/>
<!-- apple push notification channel-->
<int:channel id="apnsChannel"/>
<!-- service activator to process disruptionNotificationChannel -->
<int:service-activator input-channel="apnsChannel" ref="apnsPushNotificationService" method="pushNotification"/>
<!-- google cloud messaging notification channel-->
<int:channel id="gcmChannel"/>
<!-- service activator to process disruptionNotificationChannel -->
<int:service-activator input-channel="gcmChannel" ref="gcmPushNotificationService" method="pushNotification"/>
<!-- no op channel where message is logged for unknown devices -->
<int:channel id="noOpChannel"/>
<!-- service activator to process disruptionNotificationChannel -->
<int:service-activator input-channel="noOpChannel" ref="noOpPushNotificationService" method="pushNotification"/>
<!-- error channel to may be log to file or email or store to db in the future -->
<int:channel id="errorChannel"/>
<int:service-activator input-channel="errorChannel" ref="notificationErrorHandler"/>
Why are you starting the flow with a pub-sub channel? It's not normal to use a pub/sub channel for message distribution.
If you can use a message-driven channel adapter instead, you can add an error-channel.
You can't add an error channel to a pub-sub channel. You can, however inject an error-handler (implements org.springframework.util.ErrorHandler) and throw an AmqpRejectAndDontRequeueException when you detect a fatal error.
You can also use a Json MessageConverter in the channel instead of using a Json transformer downstream in the flow; in that case, the default error handler will detect a message conversion exception and reject the message rather than requeueing it.
/*Below Spring-integration configuration*/
/*Listener*/
<!--Reading the Message from Queue as a Listener -->
<int-jms:inbound-gateway connection-factory="MQConnectionFactory"
request-destination="ReadWsRequestQueue"
request-channel="ReadWsInputChannel"
transaction-manager="hibernateTransactionManager"
error-channel="errorReadChannel"/>
/*Processing Message*/
<!--Processing the message-->
<int:chain input-channel="ReadWsInputChannel">
<int:transformer ref="ReadUnmarshaller"/>
<int:transformer ref="RequestBuilder" method="build"/>
<int:service-activator ref="ReadService" method="registerRead" />
<int:transformer ref="ResponseBuilder" method="buildResponse"/>
<int:transformer ref="ReadMarshaller"/>
<int:transformer ref="toStringTransformer"/>
/*Error Channel config*/
<!--Error channel configuration -->
<int:channel id="errorReadChannel"/>
<int:chain input-channel="errorReadChannel">
<int-jms:outbound-gateway id="jmsOutboundGateway"
connection-factory="MQConnectionFactory"
request-destination="DLQErrorQueue" />
</int:chain>
Question:
In service Activator method we are throwing a RuntimeException, which should get redirected to the error channel??
All the exceptions should go to the error-channel,
Question 2.)
Also is there any way in Spring-integration by which we can forward the exception causing actual MQ message to a separate channel?
I've configured tcp call in spring integration with following flow:
Gateway(Future call)====>Splitter(with executor)====>router(to 2 different transformers)===>Outboud-gateway===>Aggregator====>service
Aggregator is configured on receiving the reply because need to make another tcp call based on particular value received from first call, then send to service class.
I am getting problem after certain period of execution (records properly getting persisted) when everything halts, executor active count reaches max pool size and executor queue contains queued messages, and everything just halts forever and need to terminate the main process.
<int:gateway id="clientPositionsGateway" service-interface="com.example.ClientPositionsGateway" async-executor="syncExecutor">
<int:method name="fetchClientPositions" request-channel="clientPositionsRequestChannel" reply-channel="clientPositionsResponseChannel"/>
<int:method name="getSecurityData" request-channel="securityDataRequestChannel" reply-channel="clientPositionsResponseChannel"/>
</int:gateway>
<int:channel id="clientPositionsRequestChannel" >
</int:channel>
<int:channel id="securityDataRequestChannel" >
</int:channel>
<int:splitter input-channel="clientPositionsRequestChannel"
output-channel="singleClientPositionsRequestChannel"
/>
<int:channel id="singleClientPositionsRequestChannel" >
<int:dispatcher task-executor="taskExecutor"/>
</int:channel>
<int:recipient-list-router input-channel="singleClientPositionsRequestChannel" >
<int:recipient channel="singleClientCommQueryChannel" />
<int:recipient channel="singleClientTransQueryChannel" />
</int:recipient-list-router>
<int:transformer
input-channel="singleClientTransQueryChannel"
output-channel="transQueryHeaderEnricherRequestChannel"
ref="dmPOSBaseTransQueryTransformer" order="2"/>
<int:header-enricher id="transQueryHeaderEnricher" input-channel="transQueryHeaderEnricherRequestChannel" output-channel="dmQueryRequestChannel" >
<int:header name="transQueryHeader" value="TRANS_QUERY_HEADER"/>
</int:header-enricher>
<int:channel id="transQueryHeaderEnricherRequestChannel" >
</int:channel>
<int:transformer
input-channel="singleClientCommQueryChannel"
output-channel="dmQueryRequestChannel"
ref="dmPOSBaseCommQueryTransformer" order="1"/>
<int:transformer
input-channel="securityDataRequestChannel"
output-channel="secQueryHeaderEnricherRequestChannel"
ref="dmSECBaseQueryTransformer" />
<int:header-enricher id="secQueryHeaderEnricher" input-channel="secQueryHeaderEnricherRequestChannel" output-channel="dmQueryRequestChannel" >
<int:header name="secQueryHeader" value="SEC_QUERY_HEADER"/>
</int:header-enricher>
<int:channel id="singleClientCommQueryChannel" >
</int:channel>
<int:channel id="transformSecurityDataRequestChannel" />
<int:channel id="singleClientTransQueryChannel" >
</int:channel>
<int:channel id="dmQueryRequestChannel" >
</int:channel>
<int:channel id="secQueryHeaderEnricherRequestChannel" >
</int:channel>
<ip:tcp-outbound-gateway id="dmServerGateway"
request-channel="dmQueryRequestChannel"
reply-channel="dmQueryResponseChannel"
connection-factory="csClient"
reply-timeout="3600000" request-timeout="3600000"
/>
<int:aggregator input-channel="dmQueryResponseChannel"
method="aggregateClientPositions"
ref="clientPositionsAggregator"
output-channel="aggregateDataResponseChannel"
correlation-strategy-expression="headers[id]"
release-strategy-expression="size() == 1"
send-partial-result-on-expiry="true" />
<int:service-activator method="createClientPosition" input-channel="aggregateDataResponseChannel" output-channel="clientPositionsResponseChannel" ref="clientPositionsService" >
</int:service-activator>
<int:channel id="dmQueryResponseChannel" >
</int:channel>
<int:channel id="securityDataResponseChannel" />
<int:channel id="aggregateDataResponseChannel" >
</int:channel>
<int:channel id="clientPositionsResponseChannel" >
Here are gateway interface methods:
Future> fetchClientPositions(List clientList);
List getSecurityData(String symbol);
Looks like your TCP service is bottleneck.
From other side I don't understand a bit your message flow:
You have splitter, so your payload may be a List
you use recipient-list-router and here duplicate each item after splitting
Both recipients end up on tcp:outbound-gateway, but one by one, because both are within direct channels.
tcp:outbound-gateway sends a reply to the aggregator. But the last one has strange aggregation configuration: each group contains only one message by its id, and completes as a list with one message
aggregator sends reply (over service-activator) exactly to the gateway's reply-channel
So, how about other splitted items? They will be lost, because your gateway already has got reply just after first message. All other work seems redundant...