WebSphere Message Broker V8 or later support: Known limitations and problems
The following limitations or problems are identified when you use the CandleMonitor node with WebSphere® Message Broker V8 or later.
CandleMonitor node statistics is not available
Limitation: When a CandleMonitor node is placed in a message flow and the message flow with the same name appears multiple times within an execution group, the agent cannot get statistical data to display in the following workspaces:
- Monitor Node Base Statistics
- Monitor Node Broker Statistics
- Monitor Node Event Statistics
- Monitor Node Execution Group Statistics
- Monitor Node Message Flow Statistics
- Monitor Node Sub-Flow Statistics
For example, a CandleMonitor node is placed in a message flow name MF1. This MF1 message flow is deployed directly in an execution group named EX1 and also in an application within the EX1 execution group. In this case, the MF1 message flow appears twice within the EX1 execution group, which will cause the problem.
To avoid this problem, if a message flow is deployed with a CandleMonitor node, deploy it only once in an execution group. For example, if you deploy this message flow directly within an execution group, make sure that other containers (application or library) in this execution group do not contain this message flow.
CandleMonitor node cannot be placed in deployable subflows
Problem: CandleMonitor node cannot be placed in deployable subflows using WebSphere Message Brokers Toolkit 8.0.
Solution: This problem happens when you use WebSphere Message Brokers Toolkit 8.0.0.0. To use CandleMonitor node in deployable subflows, apply the fix of PMR 63949,000,672 or upgrade to WebSphere Message Brokers Toolkit 8.0.0.1 or later.