Can you set the query hint on the find? Just to see if the underlying cache will
refresh itself. And do try the other hint given by Gopal ;)
Manfred
-----Original Message-----
From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
Sent: Tuesday, July 15, 2008 5:21 PM
To: users_at_glassfish.dev.java.net
Subject: Re: RE: RE: Problem with JPA and cache
Yes, all of the Commands are executed in the same thread and the same JTA transaction. This is because in the real J2EE application the Commands are executed via stateless session beans using the local interface. In the test application, all of the EntityManager work is done within the one single thread and wrapped with a transaction. So the test application and the real application are as close as I could get them in terms of the model of EntityManager access, threading, and transactions.
Yeah, I've been through that blog and have searched most of the web I think :) To get this problem boiled down into the simple test application has taken over 100 hours of my life and a lot of my hair!
[Message sent by forum member 'bbergquist' (bbergquist)]
http://forums.java.net/jive/thread.jspa?messageID=286884
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net