Hi, did you try tunig: openjpa.AutoDetach [ depending what you do loaded(LiteAutoDetach=true) can reset the cache ] and openjpa.AutoClean (also depends the app structure)?
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-06-22 0:46 GMT+02:00 William Dazey <[email protected]>: > Hello, > I was looking around at the Broker implementation and I noticed that when > an entity becomes detached, the StateManager gets set to a > DetachedStateManager, but the StateManager in the ManagedCache still exists > and kind of bums around until the Broker is closed later. This seems to > make the ManagedCache get rather large if the Broker ends up staying open > for a long time and many entities managed. Am I missing something? Does the > ManagedCache get cleaned out some other way? >
