| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Importance of MsgId in response |
« View previous topic :: View next topic » |
| Author |
Message
|
| sarat |
 Posted: Thu May 14, 2009 10:46 pm Post subject: Importance of MsgId in response |
 |
|
Centurion
Joined: 29 Jun 2005
Posts: 136
Location: India
|
Hi Everyone,
What's the Impact if we send the same MsgId and CorrelId same as requester MsgId?
The requester MsgId should match with the response CorrelId. But what wil happend even the MsgId also same!!
Regards,
Sarat |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu May 14, 2009 11:36 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
It's not a good idea to re-use msg id and (given that you should be getting the queue manager to generate the ids) there's really no point in not doing so in terms of time saving.
Under normal circumstances multiple messages with the same id shouldn't cause problems, but don't quote me. Some of the tools associated with WMQ assume msg id is unique, and I've seen problems (in earlier versions) with odd logging errors which disappeared when I reminded the developers they should have the new msg id option in their put. Anecdotal evidence only.
The far more important thing is to always use generated ids (even the same one if you must) and not set it directly unless you've absolutely no choice at all. That's really dubious for reasons frequently discussed here. And nearly always pointless since, as I mention above, it's so easy to get a nice new generated one.
Note it's perfectly reasonable to use the request msg id in a number of response message correl ids if your design has a single request producing a number of responses.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sarat |
| Posted: Fri May 15, 2009 12:39 am Post subject: |
|
|
Centurion
Joined: 29 Jun 2005
Posts: 136
Location: India
|
Hi Vitor,
Tx for your valuable response. Yes i know this is bad idea.
But due to sudden change from F&F to R& R for one interface, it's happening like that..
Now client came back and saying.. messages are not matching and not picking the correct response...
As of my knowledge, the requester should match with the correlId of the response with the his msgid...
Please correct if am wrong
_________________
With Regards,
Sarat. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri May 15, 2009 12:58 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sarat wrote: |
As of my knowledge, the requester should match with the correlId of the response with the his msgid...
|
That's certainly the standard pattern in this situation. Points to check:
- Your requestor is using system generated ids & isn't setting it to some manual value
- The reply really does have the original msg id in the correl id (yes, I know it probably does but just check)
- The requestor is capturing the msg id correctly when the request is sent not capturing nulls
If you have ongoing problems, you might want to consider using a temporary dynamic queue for the replies.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sarat |
| Posted: Fri May 15, 2009 1:08 am Post subject: |
|
|
Centurion
Joined: 29 Jun 2005
Posts: 136
Location: India
|
Tx a lot 
Regards,
Sarat |
|
| 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
|
|
|
|
