Author |
Message
|
Carl Bloy |
Posted: Mon Aug 18, 2008 2:58 am Post subject: Error in Message Broker 6.1.0.2 |
|
|
Acolyte
Joined: 16 Dec 2003 Posts: 69 Location: England
|
All,
We're getting the following error in Message Broker on AIX....
We have an XML message that we are translating to CWF MRM message.
I've searched everywhere and can't find any reference to the following error?
<failingComponent>/{MtiImbRMErrorMap::checkRC}</failingComponent>
<componentFaultCode>ParserException.5304</componentFaultCode>
<faultDiagnostic>RM Dictionary Not Found. - 1:[[23]]; 2:[[rmLoadDictionary]]; 3:[[PN4L3BK002001]]; 4:[[]]</faultDiagnostic>
<faultSeverity>3</faultSeverity>
I've redeployed everything to make sure the correct flows and message set are deployed.
Any ideas on what may be causing this?
Any help greatly appreciated _________________ Regards
Carl |
|
Back to top |
|
 |
Gaya3 |
Posted: Mon Aug 18, 2008 3:01 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
verify your project reference and find out which msg set its using...and redeploy. _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
Carl Bloy |
Posted: Mon Aug 18, 2008 3:05 am Post subject: |
|
|
Acolyte
Joined: 16 Dec 2003 Posts: 69 Location: England
|
I've already done this, one of the first things I did. _________________ Regards
Carl |
|
Back to top |
|
 |
Gaya3 |
Posted: Mon Aug 18, 2008 3:24 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
|
Back to top |
|
 |
vaibhav_vy |
Posted: Mon Aug 18, 2008 3:28 am Post subject: |
|
|
Apprentice
Joined: 04 Aug 2008 Posts: 28
|
Please make sure you have deployed the proper message set along with message flow using that message set. The error 'RM Dictionary Not Found' typically thrown when message set is not deployed. Moreover you can check to have the right MessageSet ID. |
|
Back to top |
|
 |
Carl Bloy |
Posted: Mon Aug 18, 2008 3:36 am Post subject: |
|
|
Acolyte
Joined: 16 Dec 2003 Posts: 69 Location: England
|
Please read all the posts in the thread before responding.... _________________ Regards
Carl |
|
Back to top |
|
 |
Gaya3 |
Posted: Mon Aug 18, 2008 3:53 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
did you read Kimbert's post in that, whats your reply for that.
 _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
Carl Bloy |
Posted: Mon Aug 18, 2008 4:03 am Post subject: |
|
|
Acolyte
Joined: 16 Dec 2003 Posts: 69 Location: England
|
Yes I did read it...though its a rather old post....
I know something is badly boken, and that it's a problem with parsing the message, hence why i posted on here....
I'm using v6.1.0.2...
The error text is in my initial post _________________ Regards
Carl |
|
Back to top |
|
 |
Gaya3 |
Posted: Mon Aug 18, 2008 4:17 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
hope there are no warnings in your message set, _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
LazyBoy |
Posted: Mon Aug 18, 2008 8:24 am Post subject: |
|
|
Voyager
Joined: 04 May 2006 Posts: 78
|
Hi Carl,
After Deploying the flow and message set, please tell me what are the resources added to the execution group.
For CWF MRM Message set essentially you should be having an .dictionary file and for xml message set a .xsdzip file deployed on execution group. |
|
Back to top |
|
 |
Carl Bloy |
Posted: Mon Aug 18, 2008 11:31 pm Post subject: Solved..... |
|
|
Acolyte
Joined: 16 Dec 2003 Posts: 69 Location: England
|
This has now been solved.....
The flows had incorrectly been deployed to another execution group, without the message set. After removing these flows all is now working ok.
I was surprised though that every message was picked up my the flows in the execution group without the mesage set deployed.
Anyway you live and learn..... _________________ Regards
Carl |
|
Back to top |
|
 |
vaibhav_vy |
Posted: Mon Aug 18, 2008 11:49 pm Post subject: |
|
|
Apprentice
Joined: 04 Aug 2008 Posts: 28
|
I usually get this error because of the same reason. Thats why I stressed you to make sure to check your deployement & probably MessageSet ID.
I was surprised to see you feel offended when I offer this simple solution. |
|
Back to top |
|
 |
Carl Bloy |
Posted: Tue Aug 19, 2008 12:00 am Post subject: |
|
|
Acolyte
Joined: 16 Dec 2003 Posts: 69 Location: England
|
Actually I did check my deployment and all appeared to be correct, with no errors logged. What I've learned is next time I deploy, I'll check the open input counts to verify what is reading from the queue.
The issue I had was I had already stated that I had checked all was deployed correctly, in my initial post. Only to be asked twice if I had chacked and verified my deployment.
Anyway I have real work to do, I can't spend all day posting on here.... _________________ Regards
Carl |
|
Back to top |
|
 |
vaibhav_vy |
Posted: Tue Aug 19, 2008 1:49 am Post subject: |
|
|
Apprentice
Joined: 04 Aug 2008 Posts: 28
|
vaibhav_vy wrote: |
Please make sure you have deployed the proper message set along with message flow using that message set. The error 'RM Dictionary Not Found' typically thrown when message set is not deployed. Moreover you can check to have the right MessageSet ID. |
My earlier post was far more explanatory. I clearly indicated the need to deploy both message set & message flow together. But still people do not take positives from it.
And related to do 'real work', I dont think orgnizations do pay for sitting idle. I can understand what 'real work' meant to people who need more than a day to deploy message set & message flow together. |
|
Back to top |
|
 |
Carl Bloy |
Posted: Tue Aug 19, 2008 1:58 am Post subject: |
|
|
Acolyte
Joined: 16 Dec 2003 Posts: 69 Location: England
|
I have clearly mentioned already on more than one occasion the Message Flows and Mesage Set were correctly deployed to the relevant execution group. Unknown to me the message flows had been deployed to another execution group without the message set being deployed.
Keep up the hard work... Happy posting... _________________ Regards
Carl |
|
Back to top |
|
 |
|