#228 History service can't connect to DB

[Sebastien DURIS]

Helo,

since my last update in 2.7.3, history service fail with
Caused by: org.hibernate.exception.GenericJDBCException: could not prepare statement [Connection is closed]

JOC can log to mariaDB whihout issue (i see sessions in my admin view).

I already tried to :

• reset states of controller
• force reset all my agent
• double check my joc install xml
• reinstall JOC

could you help me ?

[Sebastien DURIS]

my service history log
and java version :
root@js7:/var/log/js7/joc# java -version
openjdk version "17.0.13" 2024-10-15
OpenJDK Runtime Environment (build 17.0.13+11-Debian-2deb12u1)
OpenJDK 64-Bit Server VM (build 17.0.13+11-Debian-2deb12u1, mixed mode, sharing)

[Andreas]

Hi Sebastien,

your Database Server closes the connection that was established by JOC Cockpit. You find errors in the log file such as:

Connexion ré-initialisée par le correspondant

As a first guess, check if the max. packet size configured with your MariaDB DBMS is too small. Typically this is specified with a my.cnf configuration file like this:

[mysqld]
max_allowed_packet=50M

A minimum size of 50 MB is recommended. In case that your jobs create large log output, increase the size to 100 MB. There is no harm to the Database Server from this setting, it's just a maximum. JOC Cockpit has to be restarted after you applied changes to the Database Server in order to refresh connections from the pool.

The related error should be explained from the Database Server's error log file.

[Sebastien DURIS]

Really nice ! thanks a lot

Didn't found DB tuning in docs, perhap i missed it ....