Message-ID: <gh-pgjdbc-pgjdbc-3530-c2676800631@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Sun, 23 Feb 2025 11:27: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: davecramer
X-GitHub-Comment-Id: 2676800631
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-2676800631
Content-Type: text/plain; charset=utf-8

> > the stacktraces do not match the line numbers from 42.7.5. Could you please provide a coherent version number + stacktrace pair?
> 
> My apologies, we upgraded to 42.7.5 this week but the stack traces are from last week. The stack traces are from 42.7.4.
> 
> > I do not believe this has anything to do with the postgresql database instance.
> 
> Correct, when I say "the server" I'm referring to the JVM which is hosting the PG JDBC driver. It is the one experiencing an OOM.

In which case I agree with @bokken that this is an error that probably should not be recovered from