| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message retrieval |
« View previous topic :: View next topic » |
| Author |
Message
|
| Kateel |
 Posted: Tue Jan 23, 2007 11:38 am Post subject: Message retrieval |
 |
|
Novice
Joined: 01 May 2006
Posts: 17
|
Hi
Is it possible to check from inside a flow whether the previous message that was put(MQOutput node) by the flow was consumed by some application?.
We dont' want to use Database option since there is no WMQI response phase for these messages and as a result applications also would have to coordinate with Database to make this technique work
Thanks |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Jan 23, 2007 11:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can use COA/COD reports. That will help.
But you're straying very dangerously close to a) message affinity, or b) breaking the logical separation between sender and receiver.
If you really need to do this, use a request/reply pattern.
Re-examine your *business* requirements, from a *business* perspective - don't get hung up on how to implement them.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Kateel |
| Posted: Tue Jan 23, 2007 3:58 pm Post subject: Q |
|
|
Novice
Joined: 01 May 2006
Posts: 17
|
Sorry I did not provide more details in my previous post.
In out environment, there are several QMGRs sending input messages to a particular Broker queue. The flow will process and rout the messages to one output queue. But as per the business requirement, the routing should be delayed until the output queue doesnot have any messages that originated from the Input QMGR.
So just before routing, I need to browse the output queue and make sure there isn't any messages with MQMD.Replytoqmgr = 'ReplyToQMGR of the present message'. Else delay till the above condition is true. MQGet and timer nodes will simplify this problem but I am stuck with getting this wierd queue status thing.
I agree, it is always better to have a database and have a response processing as well. But that is not likely since we have a very stable applications moreover applications are huge and quite complex so can't be changed for time being at least.
Would appreciate any help.
Thanks. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jan 23, 2007 4:20 pm Post subject: Re: Q |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Kateel wrote: |
Sorry I did not provide more details in my previous post.
In out environment, there are several QMGRs sending input messages to a particular Broker queue. The flow will process and rout the messages to one output queue. But as per the business requirement, the routing should be delayed until the output queue doesnot have any messages that originated from the Input QMGR.
So just before routing, I need to browse the output queue and make sure there isn't any messages with MQMD.Replytoqmgr = 'ReplyToQMGR of the present message'. Else delay till the above condition is true. MQGet and timer nodes will simplify this problem but I am stuck with getting this wierd queue status thing.
I agree, it is always better to have a database and have a response processing as well. But that is not likely since we have a very stable applications moreover applications are huge and quite complex so can't be changed for time being at least.
Would appreciate any help.
Thanks. |
Very bad design.
The server application should take in messages from which ever qmgr and reply with the replyto information on the request message.
This looks like the service is looking for message affinity which is more often then not a bad design!
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jan 23, 2007 4:28 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
That sounds like you're trying to manage performance.
This is the wrong way to do that. You should scale up the receiving process so it can handle the expected load in a timeframe that matches the SLA.
What should happen to a message that can't be put to the output queue because the output queue has messages on it?
Should it just hang around in Broker until later?
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
