LIST_DOCUMENTS return incorrect results when there is an issue of DB connection

Data Services
1

Hi, recently I got an extraordinary issue when I tried to load the documents after there are some issues related to the database connection.
The database connection issue has the log as below:

2025-05-20 09:55:27,059 [66303_ClusterManager][WARN ][com.zaxxer.hikari.pool.PoolBase         ][u:] - HikariPool-2 - Failed to validate connection org.postgresql.jdbc.PgConnection@909c62a (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2025-05-20 09:55:37,070 [66303_ClusterManager][WARN ][com.zaxxer.hikari.pool.PoolBase         ][u:] - HikariPool-2 - Failed to validate connection org.postgresql.jdbc.PgConnection@12eb3bef (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2025-05-20 09:55:39,153 [uartzSchedulerThread][WARN ][com.zaxxer.hikari.pool.PoolBase         ][u:] - HikariPool-2 - Failed to validate connection org.postgresql.jdbc.PgConnection@7b1018cc (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2025-05-20 09:55:47,081 [66303_ClusterManager][WARN ][com.zaxxer.hikari.pool.PoolBase         ][u:] - HikariPool-2 - Failed to validate connection org.postgresql.jdbc.PgConnection@4a4aa8e9 (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2025-05-20 09:55:47,083 [66303_ClusterManager][ERROR][cheduling.quartz.LocalDataSourceJobStore][u:] - ClusterManager: Error managing cluster: Failed to obtain DB connection from data source 'springNonTxDataSource.quartzScheduler': java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30040ms.
org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'springNonTxDataSource.quartzScheduler': java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30040ms.
	at org.quartz.impl.jdbcjobstore.JobStoreCMT.getNonManagedTXConnection(JobStoreCMT.java:168)
	at org.quartz.impl.jdbcjobstore.JobStoreSupport.doCheckin(JobStoreSupport.java:3322)
	at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.manage(JobStoreSupport.java:3935)
	at org.quartz.impl.jdbcjobstore.JobStoreSupport$ClusterManager.run(JobStoreSupport.java:3972)
Caused by: java.sql.SQLTransientConnectionException: HikariPool-2 - Connection is not available, request timed out after 30040ms.
	at com.zaxxer.hikari.pool.HikariPool.createTimeoutException(HikariPool.java:696)
	at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:181)
	at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:146)
	at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:128)
	at org.springframework.scheduling.quartz.LocalDataSourceJobStore$2.getConnection(LocalDataSourceJobStore.java:140)
	at org.quartz.utils.DBConnectionManager.getConnection(DBConnectionManager.java:108)
	at org.quartz.impl.jdbcjobstore.JobStoreCMT.getNonManagedTXConnection(JobStoreCMT.java:165)
	... 3 common frames omitted
Caused by: org.postgresql.util.PSQLException: This connection has been closed.
	at org.postgresql.jdbc.PgConnection.checkClosed(PgConnection.java:993)
	at org.postgresql.jdbc.PgConnection.setNetworkTimeout(PgConnection.java:1694)
	at com.zaxxer.hikari.pool.PoolBase.setNetworkTimeout(PoolBase.java:561)
	at com.zaxxer.hikari.pool.PoolBase.isConnectionDead(PoolBase.java:168)
	at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:170)
	... 8 common frames omitted

I send a request to the BAP server as below:

POST <My Domain>/api/v2/rpc
Authorization: Bearer <my token>
Content-Type: application/json

[
    {
        "jsonrpc":"2.0",
        "id":"listModels-0",
        "method":"LIST_DOCUMENTS",
        "params":{
            "documentModelName": <My model name>
        }
    }
]

Then, the response didn’t make sense to me. It said there were one entry (fullSize =1), but the entries field was empty.

[
	{
		"jsonrpc": "2.0",
		"id": "listModels-0",
		"result": {
			"fullSize": 1,
			"page": {
				"offset": 0,
				"limit": 10
			},
			"entries": []
		}
	}
]

This document exists in the database. So I think it might be related to the index issue.
Does anyone have idea where I can have a look to find out the root cause? And how can I verify if the index is currently correct?

2

Hi @son-fast-shard ,

please report a bug ticket with your version of Data Services and described behavior.

If there is an error with the connection, the server should report an error too, not return inconsistent results as a correct response.