1

I searched a lot for this and couldnt find any help. here is the problem I am facing. I am using Spring Integration Inbound and outbound gateways for synchronous request response experience. I see everything work great but not 100% of the times. The inbound gateway on server side (when in debug mode) seem to be sending the message on the channel that should land up finally in the outbound queue to the client. I can see pre-send and post-send debug logs of spring integration. The problem is the client still times out. No its not the JMSCorrelationID. Its populated fine and client does get responses most of the times. So I got a Tibco trace log. According to that what I see is that -

- the client does create a producer on Q1.
- client puts a message on Q1
- server does pick it up and acknowledge
- client creates a consumer with correlation id as selector on Q2
[In successful cases]
   - server creates a producer on Q2
   - server produces a message on Q2
   - client picks up the message from Q2
   - client acks the message on Q2.
[only in success cases above 4 steps]
- in 10 seconds (client side gateway outbound timeout) times out..
- producer and consumer on both queues disconnect.

We dont see the 4 successful steps above in failure cases.

This tells me that the inbound gateway on server side is missing some property on JMS connections settings making it lazy connect or delayed connect etc. But not able to pinpoint.

I am just putting the symptoms of my problems here.

Makarand Kashikar
  • 23
  • 4
  • Looks like I failed in formatting the question properly. My Apologies in advance. – Makarand Kashikar Aug 07 '15 at 21:48
  • You can edit your question. From other side your issue isn't clear. Share, please, some config to reproduce (Although we do testing on the Embedded ActiveMQ...). Maybe an issue with your Tibco and it just doesn't allow you create more concurrent connections?.. – Artem Bilan Aug 07 '15 at 21:51
  • Thanks I edited the question to clear the steps. Dont think the number of concurrent connection is an issue here as I am just testing this setup with a cache on the server side being used to respond back to client. I will try to come up with a small quick configuration as sample. But I thought before I do that I will put up the symptoms here to see if any one has gone thru this experience and knows the solution. – Makarand Kashikar Aug 07 '15 at 22:01

0 Answers0