Skip to main content

Jama Connect Help

Configure Liveness and Readiness Probe settings (KOTS)

Liveness and Readiness Probes are an effective tool for recovering from application failures and must be used with caution.

Liveness Probes check if a container is running correctly. They identify and fix issues if a container becomes unresponsive or gets stuck. If a liveness probe fails, Kubernetes restarts the container.

Readiness Probes check if a container is ready to accept incoming traffic. If a Readiness Probe fails, Kubernetes stops sending traffic to the container until it passes. A Pod is only considered ready when all its containers are ready.

For more information, see Kubernetes Configure Probes.

Important

Configure these settings carefully to ensure they reflect unrecoverable application failures, such as deadlocks. Adjustments to Liveness and Readiness Probe default settings must consider how your KOTS environment is currently performing. Contact Jama Support before changing these settings from their defaults.

Requirements

  • Your environment must be running Jama Connect 9.6.7 or later.

To configure Liveness and Readiness Probe settings:

  1. On the KOTS Admin Console, go to the Config section.

    KOTS_config_tab_liveness_settings.png

  2. Scroll to the Core Jama Application Settings section, and select Show Advanced Settings.

    KOTS_core_jama_app_settings_show_adv_settings.png

  3. Scroll to the Liveness Probe section and complete the settings.

    KOTS_Liveness_Probe_section.png

    • Initial Delay (in seconds)

    • Period (in seconds)

    • Timeout (in seconds)

    • Success Threshold (in seconds)

    • Failure Threshold (in seconds)

  4. Scroll to the Readiness Probe section and complete the settings.

    KOTS_Readiness_Probe_section.png

    • Initial Delay (in seconds)

    • Period (in seconds)

    • Timeout (in seconds)

    • Success Threshold (in seconds)

    • Failure Threshold (in seconds)

  5. Scroll to the Advanced Database Settings section, select Show advanced database settings, and complete the settings.

    KOTS_Adv_Database_Settings.png

    • Database connection parameters

    • SAML database schema connection parameters

    • OAuth database schema connection parameters

  6. Scroll to the bottom of the page, and select Save config.

A message confirms that your settings were saved.

Your changes won’t take effect until you deploy the new sequence.