Optimize might fail to monitor Integration Server clusters.Infrastructure Data Collector might fail to monitor an Integration Server cluster. The issue occurs when all nodes from the cluster were discovered using a non-primary port.

The issue is resolved.

When Infrastructure Data Collector monitors a Terracotta Server, the BAM_EVENT_TMP and BAM_EVENT_TMP_ATTR tables might become very large. The issue occurs when the Terracotta Server is down.

The issue is resolved.

The Optimize Monitored Components page might not display an Integration Server (IS) package.

The Monitored Components page in My webMethods might not display a discovered IS Package in the list of monitored components. As a result, you might not be able to monitor the IS package. The issue occurs when an IS package does not contain a service.

The issue is resolved.

Infrastructure Data Collector might hang during a discovery process.

Infrastructure Data Collector might hang in "Running" status during a discovery process if uncaught throwable errors occur during the process.

The issue is resolved.

Optimize does not display a warning when you delete an asset of type "JMX Configuration".

In the Discovered Assets panel on the Assets page in My webMethods, when you select an asset of type "JMX Configuration" and click Delete, Optimize does not display a warning message that all associated monitored components and associated KPIs will be deleted from the system.

The issue is resolved.

When Infrastructure Data Collector monitors a Universal Messaging realm, and the realm is offline, the wrapper log starts filling with the following exception message:

"RealmUnreachableException: Realm is currently not reachable".

The issue is resolved.

Platform Manager might hang while monitoring a Universal Messaging realm. The issue occurs when the Universal Messaging realm is configured incorrectly, or when the Universal Messaging realm is connected to a remote Universal Messaging realm, which is offline.

The issue is resolved.

When Platform Manager is configured to monitor Universal Messaging (UM), the UM log might repeatedly log the same error message.

When Platform Manager attempts connecting to a Universal Messaging interface using the UM plug-in for Platform Manager, the following error might be logged repeatedly in the nirvana.log file:

"not authorised to connect on interface".

The issue occurs when the Allow Client Connections option is unchecked for the Universal Messaging interface to which Platform Manager connects.

The issue is resolved.