The error messages that might be generated
during a deployment are listed below with an explanation:
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 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 to do with broker
status change, which it tries to do 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 user ID is present in the User Name Server's
domain.
Message BIP2045- Scenario: Error message BIP2045 is displayed
in the Message Brokers 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 can happen in the following circumstances:
- you try to deploy from a second Configuration
Manager;
this scenario is not supported.
- 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 this is not the problem, 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 and mqsichangebroker commands.
Message BIP2242- Scenario: Error message BIP2242 is displayed.
- Explanation: The deploy (configuration change) request was not
accepted before the broker timeout ConfigurationTimeout (default 300
seconds) expired. The timeout needs to be long enough for the message flow
to complete processing its current message and then accept the deploy request.
- Solution: Set these timeouts using the -g and -k parameters
of the mqsicreatebroker and mqsichangebroker commands.
- 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
Event 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.