standards setting should be able to handle this...
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Bordet,
|Simone
|Sent: Thursday, March 29, 2001 6:29 AM
|To: '[EMAIL PROTECTED]'
|Subject: RE: [JBoss-user] ejbPassivate... Again...
|
|
|Hey Fabio,
|
|> Here is my jboss.xml:
|>
|> ------------------ CUT HERE -----------------------
|> <?xml version="1.0" encoding="Cp1252"?>
|>
|> <jboss>
|> <secure>false</secure>
|> <container-configurations>
|> <container-configuration
|> configuration-class="org.jboss.ejb.deployment.StatefulSessionC
|> ontainerConfiguration">
|>
|> <container-name>default</container-name>
|> <call-logging>true</call-logging>
|>
|> <container-invoker>org.jboss.ejb.plugins.jrmp.server.JRMPConta
|> inerInvoker</container-invoker>
|>
|> <instance-pool></instance-pool>
|
|Remove the above entry.
|
|> <instance-cache>org.jboss.ejb.plugins.StatefulSessionInstanceC
|> ache</instance-cache>
|>
|>
|> <persistence-manager>org.jboss.ejb.plugins.StatefulSessionFile
|> PersistenceManager</persistence-manager>
|>
|> <transaction-manager></transaction-manager>
|
|??? Here should be 'org.jboss.tm.TxManager', not empty !
|
|> <authentication-module></authentication-module>
|> <role-mapping-manager></role-mapping-manager>
|> <container-invoker-conf>
|> <Optimized>true</Optimized>
|> </container-invoker-conf>
|> <container-cache-conf>
|>
|> <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCacheP
|> olicy</cache-policy>
|>
|> <cache-policy-conf>
|> <min-capacity>1</min-capacity>
|> <max-capacity>10</max-capacity>
|> <overager-period>20</overager-period>
|
|Overager will run every 20 seconds...
|
|> <resizer-period>10</resizer-period>
|> <max-bean-age>100</max-bean-age>
|
|...and will passivate beans older than 100 seconds
|[snip]
|
|In jboss.conf, add 'Debug' console logging, start JBoss, deploy the bean,
|from a client invoke a method on your stateful bean, then wait for
|100 secs,
|and see if there is any passivation.
|ejbPassivate seems OK, it is strange that is not called.
|Do you have the same behavior with entity beans ?
|
|Post your results,
|
|Simon
|
|_______________________________________________
|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
