My Oracle Support Banner

Impurge Taking A Long Time To Pull Tasks From Queue (Doc ID 1433297.1)

Last updated on NOVEMBER 15, 2017

Applies to:

Oracle Communications Messaging Server - Version 7.0.0 and later
Information in this document applies to any platform.

Symptoms

The impurge process runs many threads for quite some time, starting about one hour after imexpire finishes.

Normally, if impurge shows up in prstat at all, it only has 4 LWPs. But starting about one hour after imexpire runs, impurge uses more CPU time and has many more threads than normal.

You might wonder: What is it doing?  Is there a problem?

You might also observe higher than normal disk IO during this time.

However, since imexpire normally starts at 11pm (controlled by the local.schedule.expire configutil option), you might not notice any of this unless the extra impurge work starts to take long enough to still be running during peak times the next day.

Changes

Customer recently started to implement message expiration/aging policies (page 624).

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
 store.purge.maxthreads
 Other impurge tuning config options and considerations
 store.cleanupsize
 store.purge.count
 store.purge.percentage
 Trade-offs
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.