Message-ID: From: "bokken (@bokken)" To: "pgjdbc/pgjdbc" Date: Fri, 21 Feb 2025 13:36:21 +0000 Subject: Re: [pgjdbc/pgjdbc] issue #3530: JDBC Shared Timer set to cancelled In-Reply-To: References: List-Id: X-GitHub-Author-Login: bokken X-GitHub-Comment-Id: 2674573766 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-2674573766 Content-Type: text/plain; charset=utf-8 OutOfMemory is an Error not an Exception. If the pgjdbc driver can be more resilient, that is great. However consumers should strongly consider the jvm option/flag to shutdown on OOME because so many things can end up in an unexpected state. On Fri, Feb 21, 2025 at 7:30 AM Dave Cramer ***@***.***> wrote: > Thanks for the report. I would imagine that the OOM is related and when > the connection fails we are left in the unusable state > @vlsi we should probably prioritize this. > > — > Reply to this email directly, view it on GitHub > , > or unsubscribe > > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> > [image: davecramer]*davecramer* left a comment (pgjdbc/pgjdbc#3530) > > > Thanks for the report. I would imagine that the OOM is related and when > the connection fails we are left in the unusable state > @vlsi we should probably prioritize this. > > — > Reply to this email directly, view it on GitHub > , > or unsubscribe > > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >