Message-ID: <gh-pgjdbc-pgjdbc-3530-c3205022143@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 20 Aug 2025 09:10:42 +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: vlsi
X-GitHub-Comment-Id: 3205022143
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-3205022143
Content-Type: text/plain; charset=utf-8

I found one of the cases that might trigger "timer already cancelled" error: https://github.com/pgjdbc/pgjdbc/pull/3778

For instance, it would heal @lfgcampos' "NPE from StatementCancelTimerTask in run"
 case: https://github.com/pgjdbc/pgjdbc/issues/3530#issuecomment-2948773054

I'm not sure if there are the other cases though