Global Flush Configuration With Multiple Clusters (Doc ID 2566256.1)

Last updated on SEPTEMBER 19, 2023

Applies to:

Goal

CCB v.2.7.0.1.0

There is an issue with Global Flush and believe it's related to having multiple clusters in the domain.  Following document instructions in Oracle Utilities Application Framework v4.3.0.2.0 Global Flush Setup, when setting up the JMS Server, it only allows to connect to one cluster.
Pending on the cluster selected, noticed that the Global Flush does not start. and see this in the logs:

  2019-06-13 11:49:02,778 [[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR (common.cache.CacheFlushJMSManager) (1631103356) Could not start flush listener for ServiceCacheFlusher. Please check JMS configuration.
javax.naming.NameNotFoundException: Unable to resolve 'jms.OUFlushResponseTopic'. Resolved 'jms'

or

Global flush request was not successful. Please check log for details. Will perform local flush instead
All info flushed

Looks like you are only allowed to assign the JMSServer to one node or cluster. Based on this setting, global flush does not work on any other cluster but the one assigned to the JMSServer during JMS Server creation for Global Flush.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.