JDBC_PING ‘Invalid object name’ Error in Keycloak 26.2.5 #40112

ariferol · 2025-05-31T02:59:06Z

ariferol
May 31, 2025

📄 Issue Summary
Version 26.2.4 was working perfectly in my test environment. However, after upgrading to the newly released version 26.2.5, I started seeing error logs in the console.

🔧 cache-ispn.xml Configuration
This configuration was working fine with version 26.2.4:

<jgroups>
    <stack name="mssql-jdbc-ping-tcp" extends="tcp">
        <TCP external_addr="${env.JGROUPS_DISCOVERY_EXTERNAL_IP:127.0.0.1}" />
        <JDBC_PING2 
            connection_driver="com.microsoft.sqlserver.jdbc.SQLServerDriver"
            connection_username="${env.KC_DB_USERNAME}" 
            connection_password="${env.KC_DB_PASSWORD}"
            connection_url="jdbc:sqlserver://${env.KC_DB_URL_HOST}:${env.KC_DB_URL_PORT:1433};databaseName=${env.KC_DB_URL_DATABASE}${env.KC_DB_URL_PROPERTIES:}"
            initialize_sql="IF NOT EXISTS (SELECT 1 FROM sys.schemas WHERE name = '${env.KC_DB_SCHEMA:dbo}') BEGIN EXEC ('CREATE SCHEMA [${env.KC_DB_SCHEMA:dbo}] AUTHORIZATION [dbo]') END; IF NOT EXISTS (SELECT 1 FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_TYPE='BASE TABLE' AND TABLE_NAME='JGROUPS_PING' AND TABLE_SCHEMA='${env.KC_DB_SCHEMA:dbo}') CREATE TABLE ${env.KC_DB_SCHEMA:dbo}.JGROUPS_PING (address varchar(200) NOT NULL, name varchar(200) NULL, cluster_name varchar(200) NOT NULL, ip varchar(200) NOT NULL, coord bit NULL, constraint PK_JGROUPS_PING PRIMARY KEY (address));"
            insert_single_sql="INSERT INTO ${env.KC_DB_SCHEMA:dbo}.JGROUPS_PING (address, name, cluster_name, ip, coord) values (?, ?, ?, '${env.JGROUPS_DISCOVERY_EXTERNAL_IP:127.0.0.1}', ?);"
            delete_single_sql="DELETE FROM ${env.KC_DB_SCHEMA:dbo}.JGROUPS_PING WHERE address=?;"
            select_all_pingdata_sql="SELECT address, name, ip, coord FROM ${env.KC_DB_SCHEMA:dbo}.JGROUPS_PING WHERE cluster_name=?;"
            info_writer_sleep_time="500"
            remove_all_data_on_view_change="true"
            stack.combine="REPLACE"
            stack.position="MPING" />
    </stack>
</jgroups>

<cache-container name="keycloak">
    ...
</cache-container>

🛠 Temporary Fix
Initially, the cluster node data was not being inserted into the JGROUPS_PING table. I updated the following line:

insert_single_sql="INSERT INTO ${env.KC_DB_SCHEMA:dbo}.JGROUPS_PING (address, name, cluster_name, ip, coord) values (?, ?, ?, '${env.JGROUPS_DISCOVERY_EXTERNAL_IP:127.0.0.1}', ?);"
to:

insert_single_sql="INSERT INTO ${env.KC_DB_SCHEMA:dbo}.JGROUPS_PING (address, name, cluster_name, ip, coord) VALUES (?, ?, ?, ?, ?);"
After this change, node data started appearing in the table correctly.

❗ Console Error
Despite the insertion working correctly, the following error occurs during table cleanup:

2025-05-29 02:22:44,595 ERROR [org.jgroups.protocols.JDBC_PING2] (main) a0f8ca45903c-14147: failed clearing the table for cluster ISPN: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'jgroups'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:270)
...
at org.jgroups.protocols.JDBC_PING2.clearTable(JDBC_PING2.java:389)

🔍 Observation
After fixing insert_single_sql, data is correctly inserted into the table.

However, when the clearTable method is triggered (likely due to remove_all_data_on_view_change="true"), the following SQL error occurs:

Invalid object name 'jgroups'

This suggests that the JDBC_PING2 protocol might not be resolving the schema-qualified table name correctly during the DELETE or TRUNCATE operation.

ariferol · 2025-06-13T06:36:05Z

ariferol
Jun 13, 2025
Author

This answered.
To view this discussion visit https://groups.google.com/g/keycloak-user/c/6NuBsbhT9Vs

0 replies

ariferol · 2025-06-13T06:37:06Z

ariferol
Jun 13, 2025
Author

This answered.
To view this discussion visit https://groups.google.com/g/keycloak-user/c/6NuBsbhT9Vs

0 replies

Navigation Menu

Repository navigation

JDBC_PING ‘Invalid object name’ Error in Keycloak 26.2.5 #40112

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

JDBC_PING ‘Invalid object name’ Error in Keycloak 26.2.5 #40112

Uh oh!

ariferol May 31, 2025

Replies: 2 comments

Uh oh!

ariferol Jun 13, 2025 Author

Uh oh!

ariferol Jun 13, 2025 Author

ariferol
May 31, 2025

ariferol
Jun 13, 2025
Author

ariferol
Jun 13, 2025
Author