Error "Could not start flush listener for ServiceCacheFlusher. Please check JMS configuration" Occurs when RMB Application is Started and Called (i.e.flushAll)
(Doc ID 2259353.1)
Last updated on MARCH 07, 2022
Applies to:Oracle Financial Services Revenue Management and Billing - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
We are running into issues when starting RMB V188.8.131.52 Environment. Users can log into the application.
But following error occurs when the application is started and called (ie: flushAll):
ERROR (common.cache.CacheFlushJMSManager) (1403057048) 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 ''; remaining name 'jms/OUFlushConnectionFactory'
Please note this is a native setup and was upgraded to the latest RMB 184.108.40.206 release.
Also note this issue is not noted in the embedded setup.
The issue can be reproduced at will with the following steps:
- Change the URL to include flushAll.jsp (https://Server_Name/ouaf/flushAll.jsp) and Enter
Note: the error also shows up in the App server logs.
The issue has the following business impact:
Due to this issue, users cannot flush cache. Also need to understand why this occurs and how to avoid it.
Upgraded to the latest RMB 220.127.116.11 release with Native Setup.
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