WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Resolving problems when starting a broker
Use the advice given here to help you to resolve common problems that can arise when you start a broker.
When you start a broker by using the mqsistart command, the mqsicvp command is run automatically to check that the broker environment is set up correctly (for example, the installed level of Java™ is supported). On Linux and UNIX, the mqsicvp command also verifies that the ODBC environment (if specified) is configured correctly. For more information, see mqsicvp command.
For advice about specific problems that can occur when you start a broker, see the following section.
- The broker fails to start because there is not enough space in the Java TMPDIR directory or access permissions for the Java TMPDIR directory are inadequate
- Diagnostic message ICH408I is issued on z/OS when your broker fails to start
- Abend code 047 is issued with a diagnostic message
- Error message BIP2228 is issued when you try to start a second broker on Linux or UNIX
- MQIsdp client connection is refused by the broker
- Error messages BIP2604 and BIP2624 are issued when you start a broker or a new message flow
- When you start the broker through the DataFlowEngine, it cycles continually
- You have changed your logon password and cannot start your broker on Windows
- The Java installation is at an incorrect level
- Authorization errors are reported on z/OS
- Error message BIP8875 is issued when you start a broker
- Warning messages BIP8288-BIP8297 are shown in the syslog when you start a broker
- Broker startup on z/OS is very slow
- Error messages AMQ7626 and BIP8048 are displayed when you try to start a broker
The broker fails to start because there is not enough space in the Java TMPDIR directory or access permissions for the Java TMPDIR directory are inadequate
Diagnostic message ICH408I is issued on z/OS when your broker fails to start
Two scenarios are described here. Choose the appropriate
one.
Abend code 047 is issued with a diagnostic message
Error message BIP2228 is issued when you try to start a second broker on Linux or UNIX
MQIsdp client connection is refused by the broker
- Scenario: When a new MQIsdp client tries to connect to the broker, its connection is refused.
- Explanation: MQIsdp Client ID fields must be unique. If a client sends a CONN packet that contains the same Client ID as a currently connected client, the behavior is undefined.
- Solution: Ensure that Client IDs are unique.
Error messages BIP2604 and BIP2624 are issued when you start a broker or a new message flow
When you start the broker through the DataFlowEngine, it cycles continually
You have changed your logon password and cannot start your broker on Windows
The Java installation is at an incorrect level
Authorization errors are reported on z/OS
Error message BIP8875 is issued when you start a broker
Warning messages BIP8288-BIP8297 are shown in the syslog when you start a broker
Broker startup on z/OS is very slow
- Scenario: The broker startup on z/OS takes many minutes, with an extended time taken in loading the imbjplug2 .lil file.
- Explanation: When WebSphere Message Broker is run in a shared file system sysplex environment, the LPAR that the broker started in does not necessarily own the file system mount points that the broker uses. In this scenario all file accesses have to pass through the coupling facility, which adversely affects performance. During startup the broker accesses and reads many files, and loads many Java class files. All these file operations are slowed, causing longer startup times.
- Solution: For optimal startup performance, mount the directories that the broker accesses in the LPAR in which the broker is started. In particular, mount the WebSphere Message Broker installation directories locally. Mounting file systems lists the directories that WebSphere Message Broker on z/OS needs on the file system at run time; mount them locally for optimal performance.
Error messages AMQ7626 and BIP8048 are displayed when you try to start a broker
- Explanation: You see these messages when using a broker on a queue manager that is configured for global coordination with Oracle.
- Solution: Start the queue manager manually with the -si flag before starting the broker.