Hey,
going well with it. I figured it out quite well, and have a working jBoss,
given a max cache capacity large enough. I run without problems 500 client
and 1000 calls on the bench (great utility !), tomorrow I'll do some harder
test, also on different boxes: a Compaq/Alpha/Tru64Unix, a
Compaq/Intel/Windows2000.
In fact, when the cache max capacity is too small, I end up in a situation
where all cached beans are active (eg involved in a call) and a request to
insert another one arrives.
Here I kick out of the cache the last one, but I cannot passivate it, so it
will be reinserted in cache, causing the now last one to be kicked off the
cache, and so on.
What will be in your opinion the best way to handle this ? I mean what would
you like to see as warning and what would you like jBoss do (eg, undeploying
the bean, stopping, enlarge the max cache capacity temporarly, send cursing
email to me, etc :)
Marc, when release 2.1 is planned ?
Bye
Simon
