| Author |
Message
|
| sarathmattam |
 Posted: Mon Jan 05, 2009 7:35 am Post subject: Loading of Message Sets |
 |
|
Voyager
Joined: 05 Sep 2008
Posts: 94
|
Dear All,
Am working in unix box and am getting an rmLoadDictionary error for the flows using message sets. Can any body please explain
1. The process behind the loading of Message sets at runtime.
2. Why am i getting this error (from my investigation i understood that its because of some shared memory issue)?
3. How to resolve this error?
Please give a give a brief description because there are not much links available on the above topic. Or please give me some links on the same topic
Thanks in Advance
Regards,
Sarath |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Mon Jan 05, 2009 7:50 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Message sets are loaded automatically when required.
Privided they have been deployed to that execution group before they are needed....
This message is usually seen when the message set required is not deployed.
to the Execution Group where the flow is running.
It is sometimes easy to get the name of the message set wrong in a flow.
Are you sure the correct message has been deployed to the right execution group?
There was a command once (in V5) that enabled you to list the actual unique id's of all the messages sets deployed to an EG. I don't think it is available any more as there is something the ConfigMgr Proxy API that does the same job but the old comand read the Broker DB which gave the definitive picture of what was deployed.
The best way to ensure that the flow has the correct name is to reference the Message Set project in the list of referenced projects in the Message Flow. That way, when you come to fill in the Message set details in a RDC or MQInput Nodes, you only get the deails of the message sets you have referenced.
Then you can add those message set to the message flow bar file if you like and then deploy it all at the same time.
_________________
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 |
|
|
| kimbert |
| Posted: Mon Jan 05, 2009 7:54 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Please quote the full text of the error message.
If on Windows, it will be found in the Event Viewer. If on Unix or z/OS, you can do either of:
- Take a user trace
- Attach a Trace node to the failure terminal and trace $ExceptionList
Taking a user trace is good practice - you will find it very useful in all kinds of situations. |
|
| Back to top |
|
|
| sarathmattam |
| Posted: Mon Jan 05, 2009 7:57 am Post subject: |
|
|
Voyager
Joined: 05 Sep 2008
Posts: 94
|
Thanks a lot for your quick reply..
Am sure that the whatever deployed is correct. bcoz it work for some time. So what i want know is how the loading of message set is related to DB and how its happening? Is there any parameter which i can increase so that the shared memory issue will get resolved?
Thanks in advance..
Regards,
Sarath |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Jan 05, 2009 8:27 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| You have not presented us with any evidence that this is a shared memory issue. Please quote the full text of the error message, and any others which were issued at the same time. |
|
| Back to top |
|
|
|
|
