Hi Michael
I am no expert on the matter, but what is your shared mode in your
persistence.xml ?
If I am reading the below correctly, you would not need to do @Cache
modifications if your mode is correct. The cache should be shared in the
container.
http://wiki.eclipse.org/EclipseLink/Examples/JPA/Caching
Please let me know if it helps or not.
regards
Richard.
On 4 April 2011 09:49, <forums_at_java.net> wrote:
> Hello,
>
> we have a serious problem with the entity caching of GlassFish 3.0.1. We
> want
> to run multiple application servers on top of the same database.
>
> Our Application uses JPA entities with an optimistic locking field of type
> Timestamp.
>
> After activating the entity cache GlassFish always uses cached instances
> without checking the database for any changes. So one App-server
>
> does not detect the changes of the others.
>
> We have played around with the configuration properties
> "refreshOnlyIfNewer",
> "alwaysRefresh" and "disableHits" without any progress.
>
>
>
> Need help! Any hints anybody?
>
>
>
> Thanks
>
> Michael
>
>
>
>
> --
>
> [Message sent by forum member 'Mag1c']
>
> View Post: http://forums.java.net/node/788278
>
>
>