Resolving problems that occur during deployment of message flows

Advice for dealing with some common problems that can arise during deployment of message flows.

The message flow deploys on the test system, but not elsewhere

Your deployment indicates that the broker does not exist

The Configuration Manager is trying to deploy to a broker that does not exist

The Configuration Manager reports that it is out of memory

Error messages are issued when you deploy to z/OS

Expected serialization of input is not occurring for a shared queue that serves multiple instances of a message flow on z/OS

MQe nodes do not work as expected after deployment to a WebSphere Event Broker Version 6.0 broker

Error messages are issued when you deploy

Additional error messages that might be generated during a deployment are explained in this section.

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 user ID used by the Configuration Manager 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 BIP2045
  • Scenario: Error message BIP2045 is displayed in the workbench 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 Event 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 BIP2066Start of change
  • Scenario: You have initiated a deployment request; for example, you have deployed a BAR file to an execution group. Error message BIP2066 is returned one or more times.
  • Explanation: The deployment request was not acknowledged by the execution group before the broker timeout ConfigurationChangeTimeout plus the InternalConfigurationTimeout (default 60 seconds) expired.
  • Solution: Increase these timeout values using the -g and -k parameters of the mqsicreatebroker or mqsichangebroker command. See Setting configuration timeouts for information about factors that affect timeouts and how to set appropriate values.
End of change
Start of changeMessage BIP2080
  • Scenario: The broker has started an execution group; for example, if you have issued mqsistart for the broker, or an error has occurred and the execution group is being recovered. Error message BIP2080 is displayed one or more times.
  • Explanation: The internal configuration request was not acknowledged by the execution group before the InternalConfigurationTimeout (default 60 seconds) expired.
  • Solution: Change the configuration timeout using the -k parameter of the mqsicreatebroker or mqsichangebroker command. See Setting configuration timeouts for information about factors that affect timeouts and how to set appropriate values.
End of change
Message BIP2242
  • Scenario: Error message BIP2242 is displayed.
  • Explanation: The deployment request (configuration change) was not accepted before the broker timeout ConfigurationChangeTimeout expired. This configuration 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 configuration timeouts 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 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.
Related concepts
Deployment overview
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:41:14

au16542_