Additional error messages that might be
generated during a deployment are explained in this section.
Message BIP1106 with WebSphere MQ reason code 2030
Message BIP1106 with WebSphere MQ error
AMQ7463- Scenario: Error message BIP1106 is issued with
reason code 2102 when you are deploying a large message set to a broker that
shares the queue manager with the Configuration Manager. WebSphere MQ error message AMQ7463 is
also issued with the text: The log for queue manager <queue
manager> is full.
- Solution:
- Stop the Configuration Manager using the mqsistop command:
mqsistop Configuration Manager -q -i
- Stop the broker using the mqsistop command:
mqsistop broker -q -i
- Stop the queue manager using the WebSphere MQ amqmdain command:
amqmdain end <queue manager>
- If you have WebSphere MQ Version 5 installed:
- Start WebSphere MQ Services.
- Right-click the queue manager, and click Properties
- Click the Log tab
- If you have WebSphere MQ Version 6 installed,
start WebSphere MQ Explorer, and select the Log
entry in the left pane.
- Increase the number of log primary and secondary files so that the total
size is larger than the deployment message.
- Restart the Configuration Manager using the mqsistart command.
- Restart the broker using the mqsistart command.
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.
Message BIP1536- Scenario: You have defined a Configuration Manager to
run with one user ID, and you have defined a broker to run on a different
computer with a different user ID. Deployment is successful but error message BIP1536 is
issued when you deploy message flows and message sets to
the broker.
- Explanation: The Configuration Manager is unable
to register for internal subscriptions with the broker because the broker
is running under one ID and the Configuration Manager is
running under another ID. The broker and the Configuration Manager relay
internal messages back and forth via publish/subscribe.
These messages are carried through WebSphere MQ,
which requires certain authorizations.
- Solution:
- Ensure that the broker's user ID is a member of the mqm and mqbrkrs groups.
- Define the broker's user ID on the computer where the Configuration Manager is
running.
- Define the Configuration Manager's user ID on the computer
where the broker is running.
- Ensure that all IDs are in lowercase so that they are compatible between
computers.
Messages BIP1536 and BIP7017- Scenario: Error messages BIP1536 and BIP7017 are
displayed.
- Explanation: The Configuration Manager has a
problem registering its internal subscriptions on topics that relate to broker
status change. The Configuration Manager tries to register
its internal subscriptions each time that you deploy a complete configuration.
The cause of the problem is given by the message BIP7017,
which indicates that you are running with a User Name Server configured,
but that the broker to which you are deploying does not have the Configuration Manager service
user ID in its user cache.
- Solution: Make the following checks. When you identify and correct
the problem, the subscriptions will be registered correctly the next time
you deploy:
- Ensure that the User Name Server is started.
- Ensure that the WebSphere MQ channels between
the User Name Server and the broker are started.
- Ensure that the Configuration Manager service user
ID is present in the User Name Server's domain.
Message BIP1835- Scenario: Error message BIP1835 is displayed.
- Explanation: The message set that you are deploying produces a
message set dictionary that is larger than the internal limit of 4 MB. This
problem can occur if you have many large message definitions defined to the
same message set.
The size of an exported message set is not a good indication
of the size of the message set dictionary that is generated at the time of
deployment, because the exported message set is stored as XML. XML can be
very verbose, but the dictionary has a much more compact internal format.
- Solution: Split the message definitions into several smaller message
sets.
Message BIP2045- Scenario: Error message BIP2045 is displayed
in the Message Broker Toolkit after deployment.
- Explanation: Each broker is identified by a universally unique
identifier (UUID), which is stored in the Configuration Manager when
the broker is defined. The UUID is also stored in the broker when it receives
its first deployment message. If the broker receives a deployment message
that contains a different UUID, it rejects the deployment message and issues
error message BIP2045. This problem can occur in the following
circumstances:
- You try to deploy from a second Configuration Manager;
this scenario is not supported in WebSphere Message Broker.
- You re-create the Configuration Manager but not the
broker.
- You experience problems with the WebSphere MQ channel
while you are deleting and re-creating the broker.
- Solution: Ensure that you are not using more than one Configuration Manager to
control a single broker. If your configuration is correct, follow the instructions
in the BIP2045 error message to regain control of the broker
by rebuilding the broker, and redeploying your message flow applications.
Message BIP2066- Scenario: Error message BIP2066 is displayed.
- Explanation: The deployment request was not acknowledged by the
execution group before the broker timeout ConfigurationTimeout plus
the ConfigurationDelayTimeout (default 60 seconds) expired.
- Solution: Change these timeouts using the -g and -k parameters
of the mqsicreatebroker or mqsichangebroker command.
Message BIP2242- Scenario: Error message BIP2242 is displayed.
- Explanation: The deployment request (configuration change) was
not accepted before the broker timeout ConfigurationTimeout expired.
This timeout must be long enough for the message flow to complete processing
its current message and then accept the deploy request; the default is 300
seconds.
- Solution: Set the timeout using the -g and -k parameters
of the mqsicreatebroker or mqsichangebroker command.
Message BIP7053S- Scenario: When you deploy to a broker, error message BIP7053S is
displayed.
- Explanation: This error occurs in a multi TCP/IP stack environment,
and indicates that the UNIX System Services (USS) TCP/IP environment has not
been set up correctly.
WebSphere Message Broker uses USS
functions to obtain the hostname for a particular system. The following error
message is displayed if the default hostname is not set up correctly in the
USS environment:
BIP7053S: Broker $SYS_mqsi 0 unexpected Java exception java.lang.Error:
-2103399272!java.net.UnknownHostException :
Hostname: Hostname
The hostname that is reported in the error message
is the one that has been returned to the broker as a result of the
gethostname call.
- Solution: Ensure that the TCP/IP environment is configured correctly
in USS.
Tagged/Delimited String (TDS) Validator error