| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Sometimes MRM parses ... sometimes it doesnt |
« View previous topic :: View next topic » |
| Author |
Message
|
| tammy |
 Posted: Wed Apr 30, 2008 3:33 pm Post subject: Sometimes MRM parses ... sometimes it doesnt |
 |
|
Newbie
Joined: 24 Apr 2008
Posts: 5
|
Can anyone explain the following?
I have 2 flows that consist of the following:
MQInput -> Trace -> Compute -> MQOutput
Both MQInput nodes refer to the same message set. In each case, the project is able to access the same message set project. The message domain is MRM.
Apart from the queue names, all other fields in the MQOutput are identical.
Apart from the name of the trace file, the trace nodes are identical.
Both Compute nodes have identical ESQL.
All fields in MQOutput are identical apart from the queue names.
If I send XML to the input queue on the 1st flow, the message is parsed and everything works as expected. If I send the same data to the second flow, the trace shows that the message isn't parsed and it ends up on the dead letter queue (with a helpful reason code of 65536 and ExceptionList not being traced on the MQInput catch).
The platform is Windows XP. Has anyone seen anything like this before, or got any suggestions? |
|
| Back to top |
|
 |
| tammy |
| Posted: Wed Apr 30, 2008 3:46 pm Post subject: |
|
|
Newbie
Joined: 24 Apr 2008
Posts: 5
|
Just noticed in debug that it reports ' RM Dictionary Not Found.'
However, the MQInput parser specifies the message domain as 'MRM : For binary, text or XML messages (namespace aware, validation, low memory use)'. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Apr 30, 2008 10:10 pm Post subject: What version of the Broker etc |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Please let us know the Version, fixPack and if any iFixes have been installed.
Also, how are you deploying the flows and Message Sets.
I had a 'funny' the other day when I deployed to a new broker from the toolkit, a single .bar file that contained both the Message Set and the flow that used it.
I got the same error as you. Then I deployed the Message Set in its own .bar file then I deployed the Flow again, in its own .bar file and the problem went away.
I tried to recreate the problem and found that I could not do so unless I removed the message set from the deployed broker naturally. So, I have put this down to a 'one' off.
I was using V6.1.0.1 No Ifixes.
Toolkit was V6.1.0.0 No Ifixes.
_________________
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 |
|
|
| tammy |
| Posted: Thu May 01, 2008 12:33 am Post subject: |
|
|
Newbie
Joined: 24 Apr 2008
Posts: 5
|
| 6.0.0-WS-MB-WINIA32-FP0007 |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu May 01, 2008 1:13 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
RM dictionary not found means that one of the following is true:
- the message set is not deployed
- the message set is deployed, but it does not contain the physical format specified in the 'messageFormat' property of the input message.
I suspect you could have found that out for yourself by taking a user trace and reading the error message. |
|
| 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
|
|
|
|
