My Oracle Support Banner

STCMS performance drops after producer throttling kicks in (Doc ID 1475589.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Java CAPS - Version 5.1.3 to 5.1.3 [Release 5.1]
Information in this document applies to any platform.
***Checked for relevance on 17-December-2013***

Symptoms

We have a common logging domain that all other domains feed. The primary service on this domain adds audit records form all other domains (fed by JMS) to a data base,  and at the time of the the incident when producer throttling was seen, this services was adding records to the DB at a very slow rate (about 1 every second or two) while the other domains were generating audit records for this domain at a much greater rate. As a result this common domains main queue  was constantly runnning with 100,000 records and wasn't accepting new records from the other domains.

we removed all .dbs and lock files from STCMS/Instance1 and restarted the domain until when the domain successfully started processing.

ERROR
-----------------------
26-Jun-2012 19:51:05.037 stcms WARN 1 [MessageQueue.cpp:1797]: SetThrottlePublishers() : throttle publishers for queuename=qCLSERVICETransfer
26-Jun-2012 19:58:07.344 stcms WARN 1 [MessageQueue.cpp:1810]: SetThrottlePublishers() : unthrottle publishers for queuename=qCLSERVICETransfer

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
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.