| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Ouput started changing MsgId |
« View previous topic :: View next topic » |
| Author |
Message
|
| Esa |
 Posted: Wed Mar 09, 2016 1:56 am Post subject: MQ Ouput started changing MsgId |
 |
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
I have a quite simple flow that reads a message from a queue, changes it a little and puts it in a queue.
Suddenly, after I made some changes in the ESQL and the flow, the MQ Output node started to change the MsgId.
New message ID is not selected on the node. Message context is set to "Pass All". IIB 9.0.0.4.
Message type is datagram.
I set a debug breakpoint berofe the MQ Output node. Properties and MQMD looked normal and the original MsgId was still there. For some reason MQMD had a long accounting token, that was not present in the input message and was not set byt the ESQL either.
The message in the queue has a new MsgId. Another strange thing is that Message format has changed from MQSTR to MQROOT. Which probably explains why a new msgid has been created. But what has changed messagetype, an oversized accounting token? |
|
| Back to top |
|
 |
| Simbu |
| Posted: Wed Mar 09, 2016 5:20 pm Post subject: |
|
|
Master
Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India
|
|
| Back to top |
|
|
| Esa |
| Posted: Thu Mar 10, 2016 12:35 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
Thanks for the information!
The fix pack has been withdrawn just a couple of weeks back and we had not noticed it yet. We need to start planning an upgrade.
Fortunately the problem was not caused by the fix pack, but copying message headers in an external procedure in a way that did not attach parsers to the header folders. A classic. I should have known. |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Mar 10, 2016 12:27 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Existing 9.0.0.4 users are of course still supported by IBM, but I would agree with your plans to move to 9.0.0.5.
The filenode java file locking bug has been hitting us recently and this is fixed in 9.0.0.5.
_________________
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
|
|
|
|
