| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Error Deploying on new Config Mgr |
« View previous topic :: View next topic » |
| Author |
Message
|
| pfaulkner |
 Posted: Tue Apr 22, 2003 11:50 am Post subject: Error Deploying on new Config Mgr |
 |
|
Master
Joined: 18 Mar 2002
Posts: 241
Location: Colorado, USA
|
I just set up a new Config Mgr and exported/imported several of my message sets and flows from my old one. Didn't make any other changes.
When I try to do a Full Deploy to my Broker I get this error in the log:
BIP1106S: MQSeries error detected, reason code 2030.
An error has occurred while making an MQSeries call from the Configuration Manager. The MQSeries reason code is 2030. The Configuration Manager will continue processing if it is possible to do so.
I then tried to just deploy Delta for one of my Excecution Groups and got this error:
BIP1884S: Internal error within Configuration Manager accessing message repository: exception text ''.
An internal error has been detected within the Configuration Manager code while accessing the message repository. A DOM parser exception occurred. The text of the exception is ().
I looked in the doc but don't see anything about turning trace on for the Config Mgr.
Does anyone know what would be causing these errors or where I can find info about the config mgr trace.
I did check the max msg length of all the SYSTEM.BROKER* queues and looks like they are all defined as max. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Apr 22, 2003 11:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You'll need to make sure that not only are all of your SYSTEM.BROKER.* queues set to the maximum 100 MB limit, but also your Queue Manager, and your channels, as you would otherwise to allow passing of messages of that size.
If that doesn't work, you will need to deploy each message flow individually, doing a delta deployment each time. As well, deploy each message set individually, doing a delta.
To get this started, remove all message flows and sets from each execution group, and do a force deploy. Hopefully that will clear up your invalid configuration issue.
Otherwise you may have to drop & recreate your broker or ConfigMgr, or do some editing of the DB2 tables.
Look in the administration guide for mqsichangetrace. (I think that's where it's described). |
|
| 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
|
|
|
|
