tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <rmannibu...@gmail.com>
Subject Re: findByPrimaryKey returning wrong object
Date Tue, 11 Jul 2017 06:33:24 GMT
Hi Jyothi,

Depends your code, how transactions are defined/nested/... and also what
you mean by cache (1st level, 2nd level, JCache, other)

Any sample reproducing it (preferrably on github if possible)?


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2017-07-11 0:48 GMT+02:00 jyerrami <jyothi.yerramilli@trizetto.com>:

> Hi,
>
> We are using container managed bean for persistence of database objects.
> Consistently we get a wrong object when using findByPrimatryKey function.
> The same thing works fine when we deploy it on IBM WASv8.5.5.x.
>
> IS there any known issues with how TomEE handles updating the primaryKey of
> cached objects? IS there any parameter I can set to not cache and retrieve
> the objects so findByPrimaryKey actuall returns correct object? Any help is
> greatly appreciated.
>
> Thanks.
>
>
>
> --
> View this message in context: http://tomee-openejb.979440.n4.nabble.com/
> findByPrimaryKey-returning-wrong-object-tp4682196.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message