Messages Placed in the Oracle Service Bus JMS Reporting Provider Queue are not Being Consumed or Written to the Database
(Doc ID 2365997.1)
Last updated on OCTOBER 01, 2021
Applies to:Oracle Service Bus - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
The Oracle Service Bus (OSB) Java Messaging Service (JMS) Reporting Provider Queues are increasing but the messages are not being consumed or written to the database. The default queue is dis_wli.reporting.jmsprovider.queue_auto; a custom configuration may use a different queue. The increasing messages had begun to cause a decrease in server storage space and alerted the system administrators.
The JMS Reporting Provider deployment was in an active state and had been previously un-targeted and re-targeted to the OSB Cluster in an effort to resolve the issue. Additionally, multiple restarts had been completed in an effort to resolve the issue.
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