Use JDBC Ping flag save issue when setup from CSA
search cancel

Use JDBC Ping flag save issue when setup from CSA

book

Article ID: 281626

calendar_today

Updated On: 05-10-2024

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

When trying to do a first time setup of JDBC Ping from CSA, we find this is not easily possible from CSA as upon saving the flag on one server, the second server immediately disappears from NSA. So we no longer see other servers when saving Use JDBC Ping is setup from CSA

  1. Set up 2 Clarity servers in cluster on multicast
  2. Connect to CSA, note both servers are there and available
  3. Now go to CSA - pick one server - CSA tab - note the Use JDBC Ping is unchecked
  4. Select Use JDBC Ping, Save

Expected Results: The setting to be saved, and to be able to select the other server to apply the same update

Actual Results: The setting is saved on server 1, however once we save, the server 2 is no longer accessible for update via CSA

Resolution

This is typically caused by Beacon issues if beacon service is not fully started

Workaround: Update JDBC Ping flag via properties.xml by adding useJDBCPing="true" in the nsa line as in the example below: