Hi Armin, I'm writing an application using session beans and Ojb, and deploy on Jboss in development and on WebLogic in prod. I'm facing problems with ObjectCacheDefaultImpl when the application is heavily used in prod. It seems that the synchronized statement in the cache does not behave correctly, and then the objects in he cache are corrupted.
Are you aware of this problem ? Did you face it before ? Do you have a solution ? I've implemented the following solution: I've implemented a new class for the cache, this class calling a session bean (max-bean-in-free-pool = 1). I then ensure that the synchronized access to the cache is done using the singleton session bean. What do you think of this solution ? Are you interested in the code ? David WIESZTAL. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
