W
W
Wan-Derer2021-11-11 14:31:21
Java
Wan-Derer, 2021-11-11 14:31:21

Spring and Firebird: how to fix SQLState: null and not support non-zero timeouts warnings?

Hello!
Struggling with Spring and Firebird (server v 2.5). Questions:
1. When making requests from the code, I receive the following warnings:

WARN 11008 --- [ntContainer#0-1] o.h.engine.jdbc.spi.SqlExceptionHelper : SQL Warning Code: 0, SQLState: null
WARN 11008 --- [ntContainer#0-1] o.h.engine.jdbc.spi.SqlExceptionHelper : Connection.isValid does not support non-zero timeouts, timeout value 5 has been ignored

In this case, the request passes, the data is received. But somewhere something is misconfigured. What and where to tweak?

2. Not to get up twice :) According to IDEA. I use the built-in Ultimate client to work with the database. I prescribe the connection parameters, press Test Connection and get this:
DBMS: Red Database 2.5 (ver. WI-V2.5.0.10968) Case sensitivity: plain=upper, delimited=exact Driver: Jaybird JCA/JDBC driver (ver. 4.0.4, JDBC4.3) Effective version: Firebird (ver. 2.5) Ping: 50 ms (keep-alive query results in error)
[42000][335544851] Dynamic SQL Error; SQL error code = -104; Unexpected end of command - line 1, column 8 [SQLState:42000, ISC error code:335544851]
[00000][335544436] SQL error code = -104 [42000][335544851] Unexpected end of command - line 1, column 8.

At the same time, everything works, the signs show, requests in the console work, etc. But the error is annoying. I found that the database server (?) has a non-standard terminator (end-of-line character), how can I win in queries, there are recipes, but how can I make the test in IDEA pass normally?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
W
Wan-Derer, 2021-11-11
@Wan-Derer

Tex ... I figured out the first question, I'll leave it here, suddenly it will come in handy for someone. Decided by downgrading the JDBC driver to 2.2.15 (by writing the appropriate line in pom.xml). As I understand it - the old DBMS server - the old driver :) By the way, jar for java-1.8 normally (at least for now) works under java-17.
The second question is still unanswered, the trick with slipping the old driver did not work there .....

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question