|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.
sounds good we were not able to do this previously :)
yes the bench written by Sebastien is quite good
|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.
I see, you know given the fact that most caches will run on big machines I
don't see why the "max size" should be a hard limit... it introduces
artificial problems. I am all for removing the "max"
|
|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 :)
enlarge the max, in fact remove the max requirement. What is the purpose,
that we don't run out of memory :)))
|Marc, when release 2.1 is planned ?
I am shooting for the end of this week.
Rickard stuff with EJX needs to make it in, some andy stuff, the roberto
work, some deployer stuff and this would be great...
marc
|
|Bye
|
|Simon
|
|
|
