|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
[Solved] MQ Series Message Retrival Question |
« View previous topic :: View next topic » |
Author |
Message
|
Wbrant |
Posted: Fri Aug 22, 2003 7:35 pm Post subject: [Solved] MQ Series Message Retrival Question |
|
|
Novice
Joined: 22 Aug 2003 Posts: 10
|
HI, I hope there is a solution for me.
I currenlty am running MQSeries on a Solairs 2.8 plaform. I currently have a queue called in.queue. The queue currently has approximtely 90,000 messages in it.
What i would ideally like to do is have someway delivering the messageds to multiple clients. I.E. have the message remain in the queue in til 2 separate processes have retrived them.
Is there any such functionality or do i need to completely switch a topic.
Best Regards
Bill Brant |
|
Back to top |
|
 |
EddieA |
Posted: Fri Aug 22, 2003 9:10 pm Post subject: |
|
|
 Jedi
Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles
|
Not without using intermediate queues and a utility or application to take those messages and deliver each one to 2 different queues. Then each client could read from it's own queue.
Without doing that, you could browse with one application and get with another, but there's no way on knowing if the 'browsing' application has seen the message before the 'getting' application removes it from the queue. Unless you stop the sending application, then run the 'browsing' client and when that ends, run the 'getting' client. Messy.
Cheers, _________________ Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
Back to top |
|
 |
PeterPotkay |
Posted: Mon Aug 25, 2003 2:37 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Lets say all the messages on the queue have blank CORRELIDs to start with.
The first app issues an MQGET asking for CorrelID of blank.
It proccesses any message it gets, changes the CorrelID to App1Yes, and puts it back to the queue (at the bottom of the queue).
Repeat until 2033 error (no more messages on the queue with a blank Correl ID.
The first app then does MQGETs asking for CORRELID of App2Yes.
It process any of these messages and then deletes them, since now both apps have processed them.
Repeat until 2033 error (no more messages that have processed App2)
App2 does the same thing only in reverse.
They can both be running at the same time a will very quickly process the entire queue.
 _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
Wbrant |
Posted: Sat Jan 17, 2004 12:30 pm Post subject: Thaniks |
|
|
Novice
Joined: 22 Aug 2003 Posts: 10
|
Thanks for the great answers!! Really did help me out! |
|
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
|
|
|
|