Message-ID: <gh-pgjdbc-pgjdbc-3530-c2674618170@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 21 Feb 2025 13:56:02 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3530: JDBC Shared Timer set to cancelled
In-Reply-To: <gh-pgjdbc-pgjdbc-3530@github.com>
References: <gh-pgjdbc-pgjdbc-3530@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: davecramer
X-GitHub-Comment-Id: 2674618170
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3530
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3530#issuecomment-2674618170
Content-Type: text/plain; charset=utf-8

> OutOfMemory is an Error not an Exception.
> 
> If the pgjdbc driver can be more resilient, that is great. However
> consumers should strongly consider the jvm option/flag to shutdown on OOME
> because so many things can end up in an unexpected state.
> […](#)

I think the OOM is on the server. If that is correct then we should be able to recover from that.