Hi Nils,
Nils Liebelt wrote:
Hi all,
Having some trouble with the OJB caching. I use the default implementation
which should give a global cache for all Brokers.
My Business objects have a store() method that inserts/updates this object
towards the db and removes this object from the cache wit
Nils Liebelt wrote:
Having some trouble with the OJB caching. I use the default implementation
which should give a global cache for all Brokers.
My Business objects have a store() method that inserts/updates this object
towards the db and removes this object from the cache with the
removeFromCach
>
> Hi,
>
> 1) I need to completly clear the cache. How can I clear OJB
> cache without restarting Tomcat?
pb.clearCache() (PersistenceBroker)
>
> 2) Is there any way to control maximum cache size?
None of the current cache implementation's have any size parameters. However, I
assume
le poking around. I think the InternalCache#clear()
method should call localClear() instead of localCache.clear().
Thanks much.
Paul
-Original Message-
From: Armin Waibel [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 30, 2004 2:46 PM
To: OJB Users List
Subject: Re: OJB Cache and mater
Thanks much.
Paul
-Original Message-
From: Armin Waibel [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 30, 2004 2:46 PM
To: OJB Users List
Subject: Re: OJB Cache and materialization.
Hi Paul,
you are right, the finally-block isn't a good idea. It should be safe to remove these
bloc
September 30, 2004 9:15 AM
To: OJB Users List
Subject: Re: OJB Cache and materialization.
Hi Paul,
it's fixed in CVS branch "OJB_1_0_RELEASE".
>> We are currently using OJB RC5 and are not in a position to move to >> 1.0.1 yet,
Think you are using rc6, because the "
che to false in the catch block? Of course, you'd have to provide a
setter method other than disableMaterializationCache() to turn off the
enabledReadCache flag.
Paul
-Original Message-
From: Armin Waibel [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 30, 2004 9:15 AM
To: OJB Use
Hi Paul,
it's fixed in CVS branch "OJB_1_0_RELEASE".
>> We are currently using OJB RC5 and are not in a position to move to
>> 1.0.1 yet,
Think you are using rc6, because the "materialization buffer"
(InternalCache class) was introduced after rc5 - AFAIK
It shouldn't be a problem to adapt the pat
Hi Paul,
I will have a look at this.
Stay tuned!
regards,
Armin
Nase, Paul R. wrote:
Hi,
We are encountering a problem with our cache materializing half-baked objects
when under a heavy multi-user load.
We are currently using OJB RC5 and are not in a position to move to 1.0.1 yet,
although in the f
