On Thu, 17 Nov 2011 10:47:06 +0100, Mark Rotteveel <mark@...>
wrote:

> On Thu, 17 Nov 2011 09:30:15 -0000, "tempo93fr"
> <makowski@...> wrote:
>> --- In Firebird-Java@yahoogroups.com, Mark Rotteveel <mark@...> wrote:
>>> Could you also create a tracker ticket?
>> done
>> http://tracker.firebirdsql.org/browse/JDBC-199
>
> Thanks, I will look at this tonight. Unfortunately the attached logs for
> the NullPointerException error after the unique key constraint violation
> (log_next_query.txt) does not include the stacktrace inside Jaybird. My
> initial guess though is that this is similar to the other ConnectionPool
> related issues (I believe I've seen the problem cause connection closed
> errors, the pool blocking and NPEs).
>
> Are there any specific deployment things I should be aware of?

I managed to reproduce this yesterday, but the NPE is triggered inside
eclipselink itself. It is able to successfully store a new object (with
unique title) after the previous unique key constraint violation, but the
subsequent retrieval of the updated list of movies triggers a
NullPointerException when EclipseLink is processing a list of
DatabaseFields.

I am not sure of the cause yet and the many levels of indirection
introduced by EclipseLink don't make it easy to pinpoint. The fact that
Firebird does store the object indicates that the connection itself is not
broken (or only breaks after saving the object). I have not been able to
dive deeper yesterday. I think that this might be a bug in EclipseLink
itself, I have however not yet been able to confirm or deny that.

I did go over the list of EclipseLink changes since 2.2.0, and a number of
NPEs have been fixed, but they didn't look like this problem. I won't have
time until Sunday to look further, but you might want to see if updating to
EclipseLink 2.3.1 helps solve this problem.

Mark