Bugs item #612242, was opened at 2002-09-20 13:38
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=612242&group_id=22866
Category: JBossServer
Group: v3.0 Rabbit Hole
Status: Open
Resolution: None
Priority: 5
Submitted By: Dain Sundstrom (dsundstrom)
Assigned to: Bill Burke (patriot1burke)
Summary: Small cache size totally breaks JBoss
Initial Comment:
If I use a small cache size, tons of weird errors occur
in the server.
Here is a sample small cache setting:
<container-cache-conf>
<cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
<cache-policy-conf>
<min-capacity>5</min-capacity>
<max-capacity>10</max-capacity>
<overager-period>120</overager-period>
<max-bean-age>60</max-bean-age>
<resizer-period>60</resizer-period>
<max-cache-miss-period>60</max-cache-miss-period>
<min-cache-miss-period>1</min-cache-miss-period>
<cache-load-factor>0.75</cache-load-factor>
</cache-policy-conf>
</container-cache-conf>
Attached is a file with 3 stack traces. Note, none of
these errors occur if cache size is increased to 100.
The third stack trace is cause only when read-only
methods are used with JBossCMP. This error is caused
by the cache passivating a bean that is currently being
used by a transaction, but no lock has occurred
(because of read-only). I believe that the cache
cannot tell that a bean is being used because we don't
have read locks.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=612242&group_id=22866
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
