Message-ID: <gh-pgjdbc-pgjdbc-3530-c3135538846@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 30 Jul 2025 09:35:43 +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: 3135538846
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-3135538846
Content-Type: text/plain; charset=utf-8

> Hi Team, We are also facing same issue in our production instances. We are using version 42.7.5. We have to restart JVM to bring back our services.
> 
> Stack Trace:
> 
> ```
> java.lang.IllegalStateException: Timer already cancelled.
> 	at java.base/java.util.Timer.sched(Timer.java:398)
> 	at java.base/java.util.Timer.schedule(Timer.java:194)
> 	at org.postgresql.jdbc.PgConnection.addTimerTask(PgConnection.java:1351)
> 	at org.postgresql.jdbc.PgStatement.startTimer(PgStatement.java:996)
> 	at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:516)
> 	at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:434)
> 	at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:356)
> 	at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:341)
> 	at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:317)
> 	at org.postgresql.jdbc.PgStatement.executeQuery(PgStatement.java:266)
> ```

Do you also have a corresponding OOM Exception ?