Overview

This document contains a series of cache-related tips and references that will be useful to address issues reported regularly by users working with the Jive production environment.

Information

Environment

Jive 8 and 9

Jive Cache: A list of references and tips

• Official documentation on setting up Jive cache servers for high availability.
• A description of Jive in-memory caching.
• Basic monitoring contains information about cache memory.
• A list of property settings for the cache server.
• Recommended deployment sizing.
• Cache troubleshooting.

Some basic cache-related practices followed by Jive support:

• Do not restart the cache server on its own.
• If there is a cache issue which requires restarting the cache server, perform a full restart of Jive, using this order:
  1. Jive Core Webapp server(s)
  2. Jive Cache server
  3. Jive Activity Engine service (EAE)
  4. Jive On-Premise Search service
  5. Jive Document Conversion service
  6. Jive Databases (Jive Core DB, EAE DB, Analytics DB)

The Jive Webapp services should always be the first services to be stopped and the last services to be started.

Once Webapp services are down, users are free to restart any of the other Jive services. You can see an example list of the other Jive services below.

When the user is ready to start the web app services backup, please ensure that a single node is started first and wait up to 10 minutes for it to respond to HTTP requests. After that, start the remaining web apps 20 seconds apart. This will prevent any caching issues.

If the system shuts down or restarts, the other services while the Webapp service is running, like the Cache service or Search service, then your end-users will likely begin to immediately see error messages and unexpected behavior.

• Jive’s different caches:
  • Browser Cache
  • Application Caches (cache server)
  • Rendered Content Cache (database table, more on this later)

Browser Cache

Local to every browser. Typically, a first stop in solving issues with the display and/or javascript-related problems.

Application Cache

To clear it:

1. Navigate to: Admin Console > System > Settings > Caches.
2. Select the top right tick box.
3. Select the Tick box and all the options will be selected, then scroll down to the bottom of the page.
4. At the bottom, select Clear Selected.

This clears all caches. Perform this every time a change to a running application on the database. Clearing the cache ensures the web apps will go fetch the new data put in there.  It is also another quick troubleshooting step that can be taken if something is misbehaving on the frontend.

Rendered Content Cache

Rendering something like a discussion thread or a document with lots of comments was terribly expensive in terms of performance, so we threw the HTML and styling into a table in the database for easy access, that is, a cache. The table in question is named jiveRenderedContent.

If something in the front-end like a reply to a thread, and the database doesn't agree with your eyes no matter where you look, it's likely cached in the jiveRenderedContent table.

To clear it:

1. Navigate to Admin Console > System > Settings > Cache, and clear content caches. Anything with the word "content" listed. There is no setting in the Admin Console to do that because it's not quite the same as the application caches.
2. Run the following query on the database:

UPDATE jiveRenderedContentVersion SET version = version + 1;

3. Navigate to Admin Console > System > Settings > Cache and clear the Filtered Values cache.