[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipselink-users] Logging SQL results
|
Gili,
I'm going to go out on a limb and guess that you have something
configured wrong or you're using the wrong method for data access.
This seems to me a pretty common use case and exactly what the L2
Cache is set up to do. Unfortunately I usually disable the L2 Cache
Completely, so I can't help you much, but it might help if you'd post
your EM Factory config propertiers.
./tch
On Sun, Sep 21, 2008 at 11:52 PM, cowwoc <cowwoc@xxxxxxxxxxxxxxxx> wrote:
>
> I tracked this problem down to a bug in the way warp-persist is handling
> Transaction-per-Request. The same EntityManager was being reused across
> different HTTP requests leading to the following behavior:
>
> - Request goes to Thread 1. It saves version 10
> - Request goes to Thread 2. It saves version 11.
> - Request goes to Thread 1. The query returns the cached object (version
> 10). When the thread attempts to commit this a OptimisticLockException is
> thrown.
>
> I'd still to know how to get EclipseLink to log SQL query results though...
>
> Gili
> --
> View this message in context: http://www.nabble.com/Logging-SQL-results-tp19600126p19601515.html
> Sent from the EclipseLink - Users mailing list archive at Nabble.com.
>
> _______________________________________________
> eclipselink-users mailing list
> eclipselink-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-users
>
