The Rejected Caching Primings page lists periods of time during the last 24 hours when the POA has been unable to respond immediately to all of the requests to create Caching mailboxes that it has received from GroupWise® client users. Rejected caching primings mean that some GroupWise users have been unable to change over to Caching mode immediately. The GroupWise client will retry the priming at a later time.
The POA tracks rejected caching primings in 15-minute intervals and records the date, time, and maximum number of rejected primings for each interval.
Date/Time
Displays the date and time when the maximum number of rejected caching primings occurred during its 15-minute interval.
Rejected Caching Primings
Displays the maximum number of rejected caching primings.
By default, the POA uses as much as 20 percent of its available resources for priming Caching mailboxes and moving users. If rejected caching primings are common (for example, when you first introduce Caching mode for GroupWise users), you can allocate additional POA resources for mailbox priming in ConsoleOne® (POA object > GroupWise tab > Agent Settings page > Max Thread Usage for Priming and Moves field). However, increasing thread usage so that priming proceeds more efficiently may impact GroupWise client responsiveness for other users.
If CPU utilization has not exceeded its configured threshold, you can increase the percentage of C/S handler threads available to perform primings for the current POA session. Click Maximum C/S Thread Usage for Cache Priming and Live Moves on the Configuration page.
To find out why the POA had a high number of rejected caching primings at a specific time, you can search the POA log files on the Log Files page for unusual activities during that time period.
A trademark symbol (®, ™, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. For more information, see Legal Notices.