Shared PostgeSQL database loses connection after 2h

[m-mauersberger]

We use JabRef with a PostgreSQL database and Kerberos tickets for authorization.

Now we face the problem that the client ends connection (or it gets broken?) after 2 hours. Afterwards, JabRef and the database stay still open but write events (e.g. adding an entry) result in program freeze.

Is there a timeout for connections that is caused by JabRef?

We investigated the source of the connection loss and found to be the client side (see log below, unfortunately German...).
It is read as:

  LOG:  could not receive data from client: connection has been reset by communication partner
DEBUG:  unexpected EOF on client connection

I'm not sure at the moment if it's a bug or just a setting that is possibly not reachable. Or I missed something.

Thank you in advance for helping. ;)

Server log file

2024-04-15 17:13:34.871 CEST [1203007] ***@literatur_db LOG:  Verbindung autorisiert: Benutzer=*** Datenbank=literatur_dbSSL an (Protokoll=TLSv1.3, Verschlüsselungsmethode=TLS_AES_256_GCM_SHA384, Bits=256, Komprimierung=aus) GSS (authentifiziert=ja, verschlüsselt=nein, Principal=***)
2024-04-15 19:14:58.028 CEST [1203007] ***@literatur_db LOG:  konnte Daten vom Client nicht empfangen: Die Verbindung wurde vom Kommunikationspartner zurückgesetzt
2024-04-15 19:14:58.028 CEST [1203007] ***@literatur_db DEBUG:  unerwartetes EOF auf Client-Verbindung
2024-04-15 19:14:58.028 CEST [1203007] ***@literatur_db LOG:  Verbindungsende: Sitzungszeit: 2:01:23.375 Benutzer=*** Datenbank=literatur_db Host=*** port=***

[koppor]

@m-mauersberger Nice to hear that someone really uses the Postgres integration. I was not aware of. Finally, the effort 9 years ago was worith it!

I assume that JabRef was unused for 2 horus and then connection was cut by JabRef itself.

[m-mauersberger]

Finally, the effort 9 years ago was worth it!

Absolutely! :) I appreciate the open-source concept of JabRef very much, even in terms of a local literature server. You often find a paywall at this point out there...

I assume that JabRef was unused for 2 hours and then connection was cut by JabRef itself.

Yes, that was also my experience.

I've found out that the program doesn't freeze "to death" after write request in case of connection loss, but takes very long (couple of minutes) in order to find out that connection has lost. Then you can reconnect via GUI prompt. Here, a note of connection state would be nice. Or a more active behaviour of JabRef, e.g. information about connection cut and active request to reconnect.