There is the section
<container-cache-conf>
<cache-policy>org.jboss.ejb.plugins.LRUStatefulContextCachePolicy</cache-pol
icy>
<cache-policy-conf>
<min-capacity>50</min-capacity>
<max-capacity>1000</max-capacity>
>>>>>>>>>>>>>>>>>>>>>>>>>>
<remover-period>1800</remover-period>
<max-bean-life>1800</max-bean-life>
<overager-period>300</overager-period>
<max-bean-age>600</max-bean-age>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
<resizer-period>400</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>
in standardjboss.xml that looks like what you might be interested in ..
probably... in the block marked
Vinay
----- Original Message -----
From: "François Charoy" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 11, 2001 3:30 PM
Subject: [JBoss-user] Bean Automatic Removal
>
> Hi
>
> is there a way to specify some timeout to remove a session bean from the
> container after it has been passivated. This is something that can be done
> regarding the spec, but it is not documented.
> In fact I'm looking to a way to manage unexpected client deconnection and
to
> clean the container from session bean that are not referenced anymore.
> Is there a clean way to do that.
>
> François
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
