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 AUGUST 08, 2023
Applies to:
Oracle Financial Services Revenue Management and Billing - Version 2.5.0.4.0 and laterInformation in this document applies to any platform.
Symptoms
We are running into issues when starting RMB V2.5.0.4 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 2.5.0.4 release.
Also note this issue is not noted in the embedded setup.
STEPS
-----------------------
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.
BUSINESS IMPACT
-------------------------------
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.
Changes
Upgraded to the latest RMB 2.5.0.4 release with Native Setup.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |