WebSphere Message Brokers
File: au16571_
Writer: Jane Brockbank

Task topic

This build: July 31, 2007 21:39:35

Resolving problems that occur when you start a broker

This topic contains advice for dealing with some common problems that can arise when you start a broker:

The broker and execution group are not running after you use the Default Configuration wizard

The broker or Configuration Manager fails to start because there is not enough space in the Java TMPDIR directory

The broker fails to start when it is installed on HP-UX with Oracle and DB2

Error message BIP2048 is issued on z/OS when your broker fails to start

Diagnostic message ICH408I is issued on z/OS when your broker fails to start

Abend code 047 is issued with a diagnostic message

Abend code 047 is issued in bin/bipimain

Database error message BIP2322 is issued when you start or stop a broker on Linux or UNIX

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 or BIP2624 are issued when you start a broker or a new message flow

When you start the broker through the DataFlowEngine, it cycles continually

The broker terminates with an abend on startup on AIX

You have changed your logon password and cannot start your Configuration Manager or broker

Related concepts
Brokers
Broker domains
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:39:35

au16571_ This topic's URL is: