JMS Reporting Provider Going Into Failed State When One Of Cluster Member Restarts
(Doc ID 2713367.1)
Last updated on SEPTEMBER 23, 2020
Applies to:Oracle Service Bus - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On : 184.108.40.206.0 version, OSB Core Functionality
JMS Reporting Provider going into Failed state and throwing error in server startup log
weblogic.application.ApplicationException: [OSB-Reporting:473517]The JMS Reporting Provider Database tables werent created and the JMS Reporting Data Manager didnt deploy.
There were 2 issues:
When this was resolved they were still seeing the below error in the SB Console Message Reports link.
Provider Not Available
JMS Reporting Provider is not deployed, or it is not active
Corruption with DB Reporting table.
And when server started in
Bug 8898178 - 220.127.116.11: OSB-REPORTING ARE NOT LOADED ON THE DB USER DOMAIN FAILS ON STARTUP
This is by design. Reporting tables are not created automatically if server is started in production mode. You have to create them when creating the domain.
While redeploying the "jmsreportprovider.jar" customer should take care to rename it as "JMS Reporting Provider".
This is for the Issue#2
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