| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP1538E: Unable to deploy configuration data to broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| yoon |
 Posted: Sun Oct 08, 2006 10:14 pm Post subject: BIP1538E: Unable to deploy configuration data to broker |
 |
|
Novice
Joined: 18 Aug 2006
Posts: 14
|
Hi friends,
I have try to deploy bar file to Message Broker in Solaris by using WBIMB (version 5.02 with fix pack CSD04) and increase DB2 database's configuration parameter value in APP_CTL_HEAP_SZ with 1024, APPLHEAPSZ with 1024 and DBHEAD with 1200.
Initially, I have try to deploy bar file with file size 180KB and it shows the successful to deploy, but when i have change bar file with size 617KB, it prompt the following error message.
BIP1538E: Unable to deploy configuration data to broker BKGLMD01 on queue manager GLMBKD01; WebSphere MQ reason code 2218.
An attempt was made to deploy configuration data to broker BKGLMD01 on queue manager GLMBKD01, but WebSphere MQ could not deliver the deploy request to the broker. The WebSphere MQ ReasonCode is 2218. No configuration data was deployed.
For more information on this error refer to the WebSphere MQ Application Programming Reference manual, code 2218. Correct the problem and retry the deploy operation.
So do you know what is the problem happen in here? How can i resolve the problem, may you give any advise and idea with details? Thank you.
_________________
{-'_'-}yoon |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Sun Oct 08, 2006 11:31 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi Yoon,
The Broker Queue manager and the tool kit is connected using client - Server channel.
As per the error: The Message that you are placing is too big for the channel to hold.
Please have a look in to the size of the Queue manager can hold messages.
Thanks and Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Sun Oct 08, 2006 11:36 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
Look in to the MAXMSGL() specified on a channel definition.
please look in to the Dead letter queue also, ensure that the message has reached there, if you defined it
Thanks and Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| yoon |
| Posted: Tue Oct 17, 2006 5:49 am Post subject: |
|
|
Novice
Joined: 18 Aug 2006
Posts: 14
|
hi thank you for your helping, I have solved the problem by following guide
Message BIP1538 with reason code 2218
Scenario: Error message BIP1538 is issued with reason code 2218 when you are deploying a large message set.
Explanation: The size of the message exceeds the maximum message size on the channel.
Solution: Increase the channel maxmsgl parameter on both channel pairs, at both ends:
On the Configuration Manager queue manager, issue the WebSphere MQ alter channel command:
alter chl(CM_to_BRK) chltype(sdr) MAXMSGL(104857600)
alter chl(BRK_to_CM) chltype(rcvr) MAXMSGL(104857600)
On the broker queue manager, issue the WebSphere MQ alter channel command:
alter chl(BRK_to_CM) chltype(sdr) MAXMSGL(104857600)
alter chl(CM_to_BRK) chltype(rcvr) MAXMSGL(104857600)
Stop and restart each of the channels.
_________________
{-'_'-}yoon |
|
| 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
|
|
|
|
