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 other resources
Advice for dealing with some common problems that can arise when you start resources other than a broker.
- Resources terminate during startup
- Resources hang at startup on Windows
- Error message BIP8048 is issued when you start a component
- You experience problems with the default configuration
- A "Not Found" error is issued when you click a link to a specific sample
- The Quick Tour is displayed as a blank window
- Error message BIP0832 is issued on startup
- Your execution groups restart repeatedly
- You cannot tell whether startup is complete on z/OS
- Abend code 0C1 is issued when you try to start the DataFlowEngine on z/OS
- Error message BIP2604 with return code MQRC_CONNTAG_IN_USE is issued during the start of a message flow on z/OS
- After creating or changing a configurable service, you restart your broker but your message flow does not start, and message BIP2275 is issued in the system log or Windows Event Viewer
- A device allocation error is issued
- Windows fails to recognize WebSphere Message Broker digital signatures: "Unknown Publisher"
- The create command fails, and error message BIP8022 is issued
- Your execution group restarts repeatedly with a JVM Startup failure
Resources terminate during startup
Resources hang at startup on Windows
Error message BIP8048 is issued when you start a component
You experience problems with the default configuration
A "Not Found" error is issued when you click a link to a specific sample
- Scenario: You see a "Not Found" error when you click a link to a specific sample, indicating that a URL is invalid.
- Explanation: You can view sample applications only when you use the information center that is integrated with the WebSphere Message Broker Toolkit. If you are viewing a stand-alone or online information center, you cannot access these resources.
- Solution: If you want to access samples, ensure that you are viewing the information center from within the WebSphere Message Broker Toolkit.
The Quick Tour is displayed as a blank window
Error message BIP0832 is issued on startup
Your execution groups restart repeatedly
You cannot tell whether startup is complete on z/OS
The infrastructure main program bipimain is the first process in every address space. It starts bipservice, bipbroker, or DataFlowEngine as the second process in the same address space. For each execution group, an additional address space is started. In this example, only one execution group is available.
Abend code 0C1 is issued when you try to start the DataFlowEngine on z/OS
Error message BIP2604 with return code MQRC_CONNTAG_IN_USE is issued during the start of a message flow on z/OS
After creating or changing a configurable service, you restart your broker but your message flow does not start, and message BIP2275 is issued in the system log or Windows Event Viewer
A device allocation error is issued
Windows fails to recognize WebSphere Message Broker digital signatures: "Unknown Publisher"
The create command fails, and error message BIP8022 is issued
- Scenario: Error message BIP8022 is displayed when you use the mqsicreatebroker command on Windows, even if the supplied user name and password are correct.
- Explanation: The Microsoft component "Shared File and Printer Services" is required.
- Solution: Correct this error by installing the "Share File and Printer for Microsoft network" service on the Windows system.