MQSeries.net :: View topic

PeterPotkay · Posted: Fri Oct 08, 2004 10:29 pm Post subject:

App A drops a message into an MQ Queue. WB-IMB 5.0 message flow picks it up, transforms it, and uses the HTTP Request node to send the request info to a service that only accepts http. The flow will wait wait on that http Request node until the response comes back, transform the data back into the format the original app likes, and put the reply message to the original MQMD_Reply2 info. So its one message flow that gets the request message and puts out the reply message, with an HTTP Request node in the middle of the message flow.

This kinda *feels* wrong, that the flow will be blocking on that http request. Should I worry about this?

I plan on putting multiple instances of the flow into 2 Execution Groups (the server is a 2 CPU box), so there will be multiple instances of the flow servicing the queue at the same time.

1.)When message flow A1 is waiting for the http request to come back, I am assuming the other flows can still work 100% normally, correct? The blocking of flow A1 won't disrupt anything else on the server, right?

2.) Is the length of time the flow waits on the http request node configurable, so it can give up and put the message to a catch queue?
_________________
Peter Potkay
Keep Calm and MQ On