I am definitely seeing this problem also. I have to finish code for a deadline, but tracking this down was next on my list. It does seem that the problem does not occur when disable-caching is false, but I need to make sure before this app goes into production for a large number of users.
As for the advice above about increasing the max memory limit (Xmx) I would caution that this is not a very good thing to do in general for your JVM settings unless you are sure that you application really needs all of that memory for its working set. I have spent more time than I wanted on Java performance tuning, but I have found that giving too much memory to a JVM can hurt performance almost as much as not giving enough. On 5/31/05, Marcus Brito <[EMAIL PROTECTED]> wrote: > > I see, that is very helpful to me to see that someone else has > > the error too. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
