IBM Tivoli Composite Application Manager for Applications, Version 6.2.3
The Broker does not respond
The broker does not respond when the agent requests data
from the broker but does not get a reply. This situation is caused
by a problem with the broker, but because the monitoring agent usually
detects the problem before anything else does, it appears to be a WebSphere® Message Broker Monitoring agent problem.
A broker might not respond to agent requests for several reasons,
such as:
It cannot communicate with its User Name Server.
It cannot communicate with its Configuration Manager.
There is a subtle problem with its database.
Symptoms of this problem are as follows:
The Broker_Not_Responding product event occurs in the Product
Events workspace.
The agent logs the KQIA107W and KQIA041W messages repeatedly over
several collection cycles.
Data is missing from Tivoli® Enterprise
Portal Information workspaces.
Broker system log messages might be issued, such as the BIP2080E
message and the BIP2066E message.
When you encounter this problem, try the following procedures:
Stop all WebSphere Message
Broker components and the monitoring agent.
Restart all components in the correct order, start the agent,
and determine whether broker responds.
Resetting a broker on z/OS systems
Do the following steps to reset a broker on z/OS® systems:
Stop the broker and monitoring agent.
Run component PDS jobs in this order with condition code 0 for
all steps: BIPJRSTC, BIP#DB01, BIP$DB01, BIP$DB02, BIP$DB03, BIP$DB04,
BIP$DB05
Start the broker (it does not have execution groups).
Start channels between queue managers for the broker, User Name
Server, and Configuration Manager.
Deploy the complete configuration (all types) from the Control
Center (Message Brokers Toolkit).
View any messages in the Control Center (Message Brokers Toolkit) log and system
log to ensure that the configuration is functioning correctly.
Start the monitoring agent.
Resetting a broker on distributed systems
Do the following steps to reset a broker on distributed systems:
Stop the agent and stop the broker using the –i (immediate)
option.
Empty all SYSTEM.BROKER.* queues in the queue manager of the broker.
Start channels between queue managers for the broker, User Name
Server, and Configuration Manager.
Restart the components in the correct order.
Deploy the complete configuration (all types) from the Control
Center (Message Brokers Toolkit).
View any messages in the Control Center (Message Brokers Toolkit) log and system
log to ensure that the configuration is functioning correctly. Use
the force deploy if necessary.