This is a shot in the dark but let me explain what's going on... I'm using guice + guice-servlet + guice-persist (20100927) in my current development efforts. Every method in my business logic which access the EntityManager is annotated with @Transactional. Using the Eclipse debugger, I can confirm that at the end of every Transaction the call to JpaPersistService.end() is called which removes the ThreadLocal EntityManager instance.
It seems that on subsequent requests which are handled by a thread which had already serviced a previous request, the ThreadLocal returns a previously created EntityManager (confirmed by the object id in the Eclipse debugger) which is returning a 'stale' state of the database. I'm completely at a loss of words on this and I'm going to debug it more tomorrow. If there's any chance that anybody could give any sort of insight, it will be greatly appreciated. I will update with any new info as I uncover it. Thanks in advanced, --mgbowman Note: I'm running on Java 1.6 + Tomcat 6.0.29 under OS X 10.6.4 -- You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.
