Message-ID: <gh-pgjdbc-pgjdbc-3530-c2674791292@github.com>
From: "bokken (@bokken)" <noreply+bokken@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 21 Feb 2025 15:03:47 +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: bokken
X-GitHub-Comment-Id: 2674791292
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-2674791292
Content-Type: text/plain; charset=utf-8

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

I think when he refers to "the server" he means his jvm.

> I have a Java-based server...  
> I have observed that this always starts when the server experiences an OutOfMemoryException...
> presumably the JVM is unstable at this point while the GC tries to recover...

I do not believe this has anything to do with the postgresql database instance.