AnsweredAssumed Answered

MQ2033 error in publishing to front end web application. How to verify that we are sending the right response message

Question asked by Barath S on Nov 14, 2017
Latest reply on Nov 14, 2017 by Kevin.Bowman

Hi Folks !

We are doing SV for an internet banking application. When publishing the Response message into Application response queue we face this challenge.

PFB details.

 

Message Format : Cobol fixed length message

Protocol : Copybook data protocol over MQ.

Flow :

W/O SV :

Application Server -> App Request Queue(targeted to Live Q) -> Live Request Queue -> Backed System -> Live Response Queue -> App Response Queue -> Application.

 

Queue setup :

App Request Queue(targeted to Live Q) - in Server A, Queue Manager A

Live Request Queue - Cluster Q in Server B, Queue Manager B

Live Response Queue - Cluster Q in Server B, Queue Manager B

App Response Queue - in Server A, Queue Manager A

 

With SV :

Application Server -> App Request Queue(targeted to Live Q) -> LISA Request Queue -> Take response -> LISA Response Queue -> App Response Queue -> Application

 

Queue setup :

App Request Queue(targeted to Live Q) - in Server A, Queue Manager A

LISA Request Queue - Cluster Q in Server A, Queue Manager A

LISA Response Queue - Cluster Q in Server A, Queue Manager A

App Response Queue - in Server A, Queue Manager A

 

In Brief :

The copybook and message are mapping perfectly. They are in line with the interfacing field specification documents. When verifying with the LIVE request response messages, they are matching exactly with them. The challenge is to make the response reach front end application. We are experiencing MQ2033 error(Message not available in Queue) in the application server logs.

 

What can be the reason and how to justify this ?

A. Connectivity is not established

B. Message Structure is wrong. So the queue is not picking up the message.

 

Appreciate expert advise and justification.

Can revert with any details required.

 

Thanks,

Barath.S

 

servicevirtualization #MQServiceVirtualization

Outcomes