How can this abstract method error happen?

From: Pawel Veselov <pawel(dot)veselov(at)gmail(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: How can this abstract method error happen?
Date: 2014-01-13 23:26:46
Message-ID: CAMnJ+BdqCaRbQ5n2=NdpE1jqOWtCYUu8Ym9LQaxFsD75S7nokg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Hi.

I'm getting an abstract method error problem with Postgres JDBC (top of
exception trace:http://pastebin.com/xsDKSdiE) There isn't a stable way to
reproduce this that I found. The driver is 9.1-902.

I don't quite understand how this can even happen. Looks like all the all
statement object are created by the connection object, and all connection
objects are created by the Driver. Driver always creates connection version
4, and that connection always creates statements version 4, so it should
always implement isClosed(). I never ever used any earlier drivers (so I
don't think there is C/P mess up, but I grepped my class path too).

Can anything else ever create a connection object, which can be of earlier
version?

Thank you.

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2014-01-14 00:29:28 Re: How can this abstract method error happen?
Previous Message Kevin Wooten 2014-01-04 01:07:30 Re: [GENERAL] Creating an index alters the results returned