| Author |
Message
|
| djz |
 Posted: Tue Dec 13, 2005 3:02 am Post subject: MQ response not reaching intended target M/c |
 |
|
Newbie
Joined: 13 Dec 2005
Posts: 2
|
We have a Frequent Flyer Application (FFP) for an airline say, X running on iSeries. Airline X is a part of a global alliance called Star Alliance. This application has a web interface and we use two sets of Queues, one channel pair that are a part of a single Queue Manager.
Now as part of a new development, where members of this FFP can make an upgrade request on his ticket (e.g. Economy to Business) for a flight on another airline that is a part of the Star Alliance group, our FFP connects to some middleware that belongs to star.
when request is triggered from the FFP website, we do an MQGET and send it to the star middleware using MQPUT and expect a response of success/failure from star middleware. This response we read using MQGET and send that response to FFP web using MQPUT. A separate set of queues are used fro communication between iSeries and Star Middleware which are not the same as that used between iSeries and Website. But all these queues are part of the same Queue Manager.
Now the response is expected by the web within 60 seconds. The iSeries logs show that the response is sent to the web in 15 seconds, but the web does not get a response. This remains the same problem inspite of increasing the response time on web to 120 seconds.
Can anybody help out in this issue? Just for your information, the setup between FFP Website and iSeries is a Client to Server connection while that of the iSeries to Star Midleware is Server to Server connection. |
|
| Back to top |
|
 |
| wschutz |
| Posted: Tue Dec 13, 2005 3:11 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
So a few questions:
1. Have you checked the channels to ensure that they are all running (especially between the iSeries and your machine)
2. Did you look at all the dead letter queues?
3. Any messages in system logs?
4. Are the responses 'persistent' messages (MQ can throw away NP messages)
5. Are the responses going to dynamic queues? If so, what type?
6. Are you setting a replyToQ and replyoQgr in the request messages .....
_________________
-wayne |
|
| Back to top |
|
|
| djz |
| Posted: Tue Dec 13, 2005 3:43 am Post subject: Response to the queries |
|
|
Newbie
Joined: 13 Dec 2005
Posts: 2
|
Thanks for the quick response. Our response is below.
1. All channels are running
2. Queue depth is zero in ala dead letter queues
3. Please eloborate on this
4. The reponse messages are not persistent
5. There are no dynamic queues used in this application
6. Yes |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Dec 13, 2005 4:12 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
3. Any messages in system logs?
look in AMQERR01.LOG and the equivalent on iSeries
4. The reponse messages are not persistent
Make them persistent, then perhaps they will wind up in a dead letter queue and you can see whats wrong .....
_________________
-wayne |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Tue Dec 13, 2005 3:27 pm Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| The application that responds is actually running and reading the queue you think it is right? |
|
| Back to top |
|
|
| JT |
| Posted: Tue Dec 13, 2005 4:38 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| ........but the web does not get a response. |
How do you detect this event ?
Does the application report all non-zero reason codes from the MQGET call ?
Do you see any messages accumulating on the queue when the web front-end application times-out ?
Can you confirm that the correlation id of the response message is the same as the request message ? |
|
| Back to top |
|
|
|
|
