My Oracle Support Banner

Could Not Start Flush Listener For ServiceCacheFlusher (Doc ID 2793207.1)

Last updated on JULY 23, 2021

Applies to:

Oracle Financial Services Revenue Management and Billing - Version and later
Information in this document applies to any platform.


On : version, MICC Transfer to TSC

Could not start flush listener for ServiceCacheFlusher

We are geeting below error message in managed server logs:

 - 2021-03-28 11:42:32,828 [[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] ERROR (common.cache.CacheFlushJMSManager) (289070701) Could not start flush listener for ServiceCacheFlusher. Please check JMS configuration.
javax.naming.NameNotFoundException: While trying to lookup 'jms.OUFlushConnectionFactory' didn't find subcontext 'jms'. Resolved ''
  at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException( ~[]
  at weblogic.jndi.internal.BasicNamingNode.lookupHere( ~[]
  at weblogic.jndi.internal.ServerNamingNode.lookupHere( ~[]
  at weblogic.jndi.internal.BasicNamingNode.lookup( ~[]
  at weblogic.jndi.internal.ServerNamingNode.lookup( ~[]
  at weblogic.jndi.internal.RootNamingNode.lookup( ~[]
  at weblogic.jndi.internal.WLEventContextImpl.lookup( ~[]
  at weblogic.jndi.internal.WLContextImpl.lookup( ~[]


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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