Message-ID: <gh-pgjdbc-pgjdbc-3530-c3173483031@github.com>
From: "wangkaish (@wangkaish)" <noreply+wangkaish@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 11 Aug 2025 06:58:14 +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: wangkaish
X-GitHub-Comment-Id: 3173483031
X-GitHub-Comment-Type: issue_comment
X-GitHub-Edited-At: 2025-08-11T07:02:55Z
X-GitHub-Issue: 3530
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3530#issuecomment-3173483031
Content-Type: text/plain; charset=utf-8

Hi @davecramer   
We have also encountered a similar issue. After a Java OOM, when attempting to operate on the database, we receive the message “Timer already cancelled.” Normally, when we encounter an OOM exception, the system can recover on its own, but this time it did not. Each recovery attempt fails due to “Timer already cancelled.”