| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Pick the message in bunch |
« View previous topic :: View next topic » |
| Author |
Message
|
| new_to_wmb8 |
 Posted: Tue Jun 24, 2014 11:28 pm Post subject: Pick the message in bunch |
 |
|
Centurion
Joined: 28 May 2013
Posts: 127
Location: Hyderabad, India
|
Hi All,
I have an requirement in which i have to pick the n of messages in bunch from the queue. these messages are not coming in group, all are independent messages.
i have tried using MQ input node property : All message available but i thin it will not work in that scenario as messages are not coming in bunch
any suggestion , how we can pick the n no messages from the queue using MQ input ???? we have to make n as configurable parameter
thanks in advance..  |
|
| Back to top |
|
 |
| zpat |
| Posted: Wed Jun 25, 2014 12:52 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
It's a bad design to process messages in this way. How can you be sure which message to retrieve? What happens if more arrive? It is essentially going to make the application very unreliable.
Selective retrieval from a queue is supposed to be done using MATCH on correlid or message id.
However it is acceptable to browse messages sequentially from a queue until you find the one you want and then get it.
The MQ API provides lots of support for this including locking messages under the browse cursor, getting a message under the browse cursor and so on.
The question is how much of this is exposed to WMB in the MQ nodes and the answer is not much.
However by careful use of ESQL and the MQGET node, you should be able to achieve it. It's a task for an expert though, not a beginner.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 25, 2014 7:01 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It's almost like you need to collect a set of different input messages, by characteristics of the message, and then process them as a single message.
I wonder if there's a node to do that for you? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Jun 25, 2014 8:43 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| mqjeff wrote: |
It's almost like you need to collect a set of different input messages, by characteristics of the message, and then process them as a single message.
I wonder if there's a node to do that for you? |
The problem is that (guessing here) that the 'n' value is unknown/variable.
IMHO, I feel that the Collector Node is not very good at this sort of thing.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Jun 25, 2014 10:19 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
He needs to unravel his assumptions that this is an appropriate design.
What, exactly, is this supposed to achieve and why do you think it is necessary to handle the messages in this way?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| 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
|
|
|
|
