Re: How can this abstract method error happen? - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: How can this abstract method error happen?
Date
Msg-id CADK3HHJM90fagxJuhN3qssSyEOW+ETPLSDVHLr+K_mn+_Ax_Pg@mail.gmail.com
Whole thread Raw
In response to How can this abstract method error happen?  (Pawel Veselov <pawel.veselov@gmail.com>)
Responses Re: How can this abstract method error happen?  (Pawel Veselov <pawel.veselov@gmail.com>)
List pgsql-jdbc
Is there anything else in the exception chain ?

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca


On Mon, Jan 13, 2014 at 6:26 PM, Pawel Veselov <pawel.veselov@gmail.com> wrote:
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.



pgsql-jdbc by date:

Previous
From: Pawel Veselov
Date:
Subject: How can this abstract method error happen?
Next
From: Pawel Veselov
Date:
Subject: Re: How can this abstract method error happen?