| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| URGENT: Temporary Dynamic Queue Across Applications |
« View previous topic :: View next topic » |
| Author |
Message
|
| maneshgurav |
 Posted: Thu Apr 20, 2006 1:14 pm Post subject: URGENT: Temporary Dynamic Queue Across Applications |
 |
|
Novice
Joined: 20 Apr 2006
Posts: 12
|
Hi All,
I have developed two VB.Net applications - Dispatcher and Listener. Dispatcher continuosly sends messages to REQUEST MQ Queue and Listener polls the RESPONSE MQ Queue to receive responses. Now, it has been decided to use the temporary dynamic response queues. So I need to change my applications.
Currently, the Dispatcher doesn't open the RESPONSE queue and the Listener doesn't open the REQUEST queue. But now, I need to open the RESPONSE queue in Dispatcher to get its name. Is it Ok, if I follow the following steps:
--------- Dispatcher Application -----------------
1. Open the RESPONSE queue in the Dispatcher (as shown below) but not close it (otherwise, it will get deleted)
queueIn = QM.AccessQueue("ABC", MQC.MQOO_INPUT_EXCLUSIVE | MQC.MQOO_FAIL_IF_QUIESCING, "", "ABC*", "")
2. Get and save the dynamic queue name to some database. So that the Listener can read it from the database.
replyToQueue = queueIn.Name
--------- Listener Application -----------------
3. Read the queue name from the database and open the queue.
queueIn = QM.AccessQueue(replyToQueueFromDatabase, MQC.MQOO_INPUT_EXCLUSIVE | MQC.MQOO_FAIL_IF_QUIESCING)
Please note that the Steps 1 & 2 will be executed in one application and the Step 3 in another. The dynamic queue won't be closed in the Dispatcher Application, but the Queue Manager will be.
Thank you,
Manesh |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Apr 20, 2006 2:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Wrong pattern.
Dynamic temporary queues are very well suited for a request reply pattern.
You seem to be running a request notify pattern.
The requester sends out the request and goes on.
The notify process picks up the response and notifies some other process or just sticks it into a DB.
On Request reply:
The requester sends out the request and waits for some time (x ms) for a reply to come in. On receiving the reply the requester processes it.
If the requester experiences a timeout it goes onto to whatever processing was set up for this occurrence.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
