-
1. Re: stateful Session Bean's session activation BUG
annegret Mar 22, 2002 4:29 AM (in response to sandeepjam)The default lifetime of a Stateful SessionBean (jboss 2.4.x) is 1800 seconds. After this time jboss removes the bean without calling ejbRemove. You should see an entry in server.log like
[Bean Cache] Removing from cache bean MySessionSB with id = xxxxx - Cache size = 2
[Container factory] Removing from storage bean MySessionSB with id = xxxxx
You can change these settings in standardjboss.xml
<container-configuration>
<container-name>Standard Stateful SessionBean</container-name>
...
<cache-policy-conf>
...
<max-bean-life>1800</max-bean-life> -
2. Re: stateful Session Bean's session activation BUG
sandeepjam Mar 25, 2002 5:59 AM (in response to sandeepjam)Hello !!
I have tried by putting 7200 sec like as follows:
<min-capacity>50</min-capacity>
<max-capacity>1000</max-capacity>
<remover-period>7200</remover-period>
<max-bean-life>7200</max-bean-life>
<overager-period>300</overager-period>
<max-bean-age>600</max-bean-age>
<resizer-period>400</resizer-period>
but its still passivated and removed after half an hour.
JBoss version is 2.4.3
Please advice !!
thanx. -
3. Re: stateful Session Bean's session activation BUG
annegret Mar 25, 2002 8:00 AM (in response to sandeepjam)Are You shure You changed the container-configuration used for the beans ( for SFSB normally configuration-name "Standard Stateful SessionBean" ) ?
We are using jboss 2.4.3 and it works for us.
The passivation time is configured as
<max-bean-age>
You can find the description of the container-configuration tags in the online manual
http://www.jboss.org/online-manual/HTML/ch07s16.html -
4. Re: stateful Session Bean's session activation BUG
sandeepjam Apr 2, 2002 5:29 AM (in response to sandeepjam)Many thanks..
In standardjboss.xml..there are two configuration one for Standard Stateful SessionBean and another one is jdk1.2.2 Stateful SessionBean..which has to be modified.
Well now i am modifying both and its seems that after below stated configuration :-
<min-capacity>50</min-capacity>
<max-capacity>1000</max-capacity>
<remover-period>7200</remover-period>
<max-bean-life>7200</max-bean-life>
<overager-period>300</overager-period>
<max-bean-age>600</max-bean-age>
<resizer-period>400</resizer-period
its passivated after 15 minutes but *.ser file is not removed after 1.5 hrs..still I am testing its seems that it will work but to..increase the (time before passivation) passivate time I have to modify this
'<max-bean-age>600</max-bean-age>'...please advice,,
Thanks again -
5. Re: stateful Session Bean's session activation BUG
annegret Apr 5, 2002 7:00 AM (in response to sandeepjam)yes, <max-bean-age> is the time after which the bean can be passivated. But the container looks for beans to passivate every <overager-period> seconds. So You should modify <overager-period> as well. In best case the bean is passivated after <max-bean-age> but in an adverse case the bean may be pssiavted not until <max-bean-age> + <overager-period>
The same is with <max-bean-life> - time after which the bean is ready for removal - and <remover-period> - time after which the container looks for beans to remove. In an adverse case the bean is removed not until <max-bean-life> + <remover-period>
For default the period-times are half the time of the max-bean-age or max-bean-life times.
Hope this helps
Annegret