[danielchai]

Have you received the letter I sent to you? Could you tell me what's wrong with the code?

Thanks.

[nraghuram]

I replied. I could not open your file. I had asked you to zip it using winzip and email it. I have version 8.1
raghu

[danielchai]

Sorry, I don't receive your reply. I have sent you another letter with the code compressed using Winzip, please help me check it.

Thanks!

[nraghuram]

I got your zip file. It does not have the xml descriptors. ejb-jar.xml, jboss.xml
raghu

[danielchai]

I didn't create them mannually. The JBuilder created them for me.

I have sent them to you, please check them!

Cheers!

[nraghuram]

You are removing the beans too quickly i think. I added a sleep before the remove loop and the passivation is happening.

Thread.sleep(5000000);
System.out.println("Removing the beans.....");

The relevant server.log for your info
2003-10-28 14:15:05,562 TRACE [org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy] Aging out from cache bean Statefulwith id = dmbjqr7t-l; cache size = 3
2003-10-28 14:15:05,562 TRACE [org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy] entryRemoved, entry=key: null, object: null, entry: 2209db
2003-10-28 14:15:05,562 DEBUG [org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager] Attempting to passivate; ctx=org.jboss.ejb.StatefulSessionEnterpriseContext@1e6cf07
2003-10-28 14:15:05,562 INFO [STDOUT] call ejbPassivate();
2003-10-28 14:15:05,562 DEBUG [org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager] Saving session state to: C:\jboss\server\default\tmp\sessions\Stateful-dmbjqmma-k\dmbjqr7t-l.ser
2003-10-28 14:15:05,562 DEBUG [org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager] Writing session state: statefultest.StatefulBean@178e13f
2003-10-28 14:15:05,572 DEBUG [org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager] Passivation complete; ctx=org.jboss.ejb.StatefulSessionEnterpriseContext@1e6cf07
2003-10-28 14:15:05,572 TRACE [org.jboss.ejb.plugins.StatefulSessionInstancePool] Discard instance:org.jboss.ejb.plugins.StatefulSessionInstancePool@114ef62#org.jboss.ejb.StatefulSessionEnterpriseContext@1e6cf07#null#false#class statefultest.StatefulBean


Also,
<cache-policy-conf>
<min-capacity>50</min-capacity>
<max-capacity>1000000</max-capacity>
<remover-period>1800</remover-period>
<max-bean-life>1800</max-bean-life>
<overager-period>100</overager-period>
<max-bean-age>40</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>

HTH
raghu

[danielchai]

Thanks, I see it!

But I have another problem. If we want to see the passivation quickly, which parameters should we change?

Also, I think if the thread sleeps too long, the container will remove the session bean. Is that right?

[nraghuram]

i think you can fiddle with the overager period and the max bean age. the overager period determines how often the overaging thread runs and the max bean age determines whether a particular bean should be passivated. so maybe u can try reducing these numbers.

[danielchai]

Thanks a lot!