| Author |
Message
|
| Zappa |
 Posted: Tue Nov 06, 2007 7:50 am Post subject: Unprocessable response on deploy |
 |
|
Acolyte
Joined: 06 Oct 2005
Posts: 55
Location: UK
|
We're having troubles when deploying two bar files, many other deploys work without issue. In the syslog I get the warning "BIP1513W - Unprocessable response received by Configuration Manager on input queue SYSTEM.BROKER.ADMIN.REPLY" which is empty. Shortly after the warning I get messages on the SYSTEM.BROKER.CONFIG.REPLY containing "DUMBLEDORE_RESPONCE.serializer...."
There are two brokers under one configmgr - WMB6.0.0.3 AIX5.3
Any help would be greatly appreciated. |
|
| Back to top |
|
 |
| rajmq |
| Posted: Wed Nov 07, 2007 4:13 am Post subject: |
|
|
Partisan
Joined: 29 Sep 2002
Posts: 331
Location: USA
|
| Quote: |
| We're having troubles when deploying two bar files |
Two bar files means ?
_________________
IBM Certified System Administrator - WebSphere MQ V6.0
IBM Certified System Administrator - WebSphere Business Integration Message Broker V6.0 |
|
| Back to top |
|
|
| Zappa |
| Posted: Wed Nov 07, 2007 5:32 am Post subject: |
|
|
Acolyte
Joined: 06 Oct 2005
Posts: 55
Location: UK
|
BAR files being broker archives containing message sets and flows.
32 individual bar files successfully deployed but two failed. The same two bar files deploy successfully to another broker.
Regardless if the BAR is deployed with the toolkit or the configmgr proxy API or the CLI. I checked the MQ logs as to why the BIP1513 appeared as the explanation of this BIP error says "This message has erroneously appeared on queue" but nothing untoward. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Nov 07, 2007 5:35 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
S.B.ADMIN.REPLY is the queue that contains publication messages from the broker to the Config Manager. The fact that the CM has received a message that it doesn't understand probably means that the levels of CM + broker are incompatible. Ensure that you have the broker and Config Manager at the same fixpack level; upgrade fixpacks if necessary.
Also make sure that you're not trying to deploy unsupported nodes to old brokers.
But if the problem persists, raise a PMR.
(The fact that you're seeing something on S.B.CONFIG.REPLY afterwards is just the Config Manager telling the toolkit or another application that some state has changed. It's not related to your problem; it's the CM probably just informing the toolkit what has happened, and is nothing to worry about.) |
|
| Back to top |
|
|
| Zappa |
| Posted: Wed Nov 07, 2007 6:10 am Post subject: |
|
|
Acolyte
Joined: 06 Oct 2005
Posts: 55
Location: UK
|
Thanks mqmatt. The Configmgr and broker should be the same fixpack level as they are on the same server.
Out of desperation I've deleted the execution group, recreated and redeployed.
To my amazement the deploy of the troublesome BARs now work - Nothings changed apart from the wind direction - how can this be? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Nov 07, 2007 6:18 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Phantom EG?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Thu Nov 08, 2007 6:23 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| Zappa wrote: |
| Nothings changed apart from the wind direction - how can this be? |
Open a PMR with your local meteorological office.  |
|
| Back to top |
|
|
| Zappa |
| Posted: Thu Nov 08, 2007 6:40 am Post subject: |
|
|
Acolyte
Joined: 06 Oct 2005
Posts: 55
Location: UK
|
| They'll just say that winter is on its way. Not the first time we have had phantom EG's (last time msgflows were listed twice) - I think that we need an Exorcist not a weather man! |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 08, 2007 7:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Zappa wrote: |
| They'll just say that winter is on its way. Not the first time we have had phantom EG's (last time msgflows were listed twice) - I think that we need an Exorcist not a weather man! |
Phantom EGs usually result from development teams working at cross purposes or admin teams punching buttons too impatiently or in the wrong sequence.
So a bit more governance on your processes - and staying current with maintenance levels - can go a long way towards keeping the dead in their graves.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
