Okay,  maybe I'm being daft - but I just don't get it.

from the manual 

   <max-bean-age> specifies the max age a bean can have 
   before being passivated by the overager ... the <resizer-period> 
   specifies the period of the resizer, that is a periodic task that
   runs ... Purpose of this periodic task is to shrink / enlarge
   the cache  capacity upon 3 other parameters...

So after 10 minutes of inactivity (jboss's default of 600 secs) it should be 
passivated --not destroyed.  Shouldn't I be able to continue to use the bean 
at 12 minutes (upon which the server will de-passify the bean ie. activate 
it) without the client ever being aware?

And if  <max-bean-age> is for passivation where do I specify the ultimate 
time after which a very old inactive bean (passivated or not) should actually 
be destroyed (eg. dropped connections)?

Currently it seems that the <max-bean-age> is acting as a destroyer and not a 
passivator.  Is this understanding correct?

Thanks for continuing to help.
Mike.

P.S.  As an aside I would have thought that using a min cache size (jboss's 
defalut is 50) greater than the number of active beans (3 in my development 
setup) that there would be no passivation at all.  As there is still room in 
the cache why why would jboss push out any bean (except of course those that 
should be killed -- but they should be killed and not passivated anyways)?

On Monday 16 July 2001 10:47, you wrote:
> Passivation should definitely not kill a stateful session bean.  (Does
> JBoss do this?  So far, I haven't deployed anything in JBoss that is idle
> for that long a period.)  However, I wouldn't be surprised if JBoss
> periodically aged-out unused stateful session beans.  I think that most
> good app servers will do this to clean up after clients which have died, or
> have not politely disconnected.
>
> If that's what's happening, the ideal option would be to increase the max
> bean age to accomodate your longest expected login period, but leave
> passivation as is.  If that's not what's happening, then maybe it's a bug?
>
> Mike


===================
Mike Finn
Tactical Executive Systems
[EMAIL PROTECTED]

_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to