Message-ID: <gh-pgjdbc-pgjdbc-3462-c2550568050@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 18 Dec 2024 07:35:22 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3462: Next Method of PgResultSet Throws NullPointerException Instead of SQLException
In-Reply-To: <gh-pgjdbc-pgjdbc-3462@github.com>
References: <gh-pgjdbc-pgjdbc-3462@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 2550568050
X-GitHub-Comment-Type: issue_comment
X-GitHub-Edited-At: 2024-12-18T07:37:08Z
X-GitHub-Issue: 3462
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3462#issuecomment-2550568050
Content-Type: text/plain; charset=utf-8

@butopcu , the NPE at 2119 most likely means you have two threads: one that accesses `.next()` and another one that closes the resultset (or calls `next` as well). The thing is `rows` field was **not null** at both line 2019 and 2116, and then it became null at line `2019`. It definitely means there was a concurrent thread that nullified the field.

I do not think we could do much about it, and I would suggest you try figuring out if the same `ResultSet` or `Statement` is reused across different threads (e.g. `static ResultSet` or `static Statement`).