This section contains hints and tips for common problems that may occur while running the IBM Lotus Expeditor micro broker.
If you are seeing strange or unexpected behavior, ensure that you follow ../com.ibm.rcp.tools.doc.appdev/mb_guidanceondeploymentenvironments.html information in Developing Applications for Lotus Expeditor
The primary problem determination mechanism is the log, which contains error, warning and informational messages. For example, messages are logged when the broker starts up, and a message is logged whenever a client connects to the broker.
You can query detailed information on the state of the micro broker using the administrative API. You can query individual attributes of the broker, such as how many clients are connected, or how many messages have been received. If you want to query multiple attributes at one time, you can also request a state snapshot, which produces a file containing information on the broker state. Note that the format of this file is subject to change, but it can be useful when debugging an application. For example, to take a snapshot using the admin API:
Trace trace = myBroker.getTrace();
Parent topic: Troubleshooting the Lotus Expeditor Client: XPD621