有狀態工作階段 Bean(Stateful Session Bean)會把實例狀態持續保存在記憶體中,如果一直不釋放,叢集與高負載環境下很快就會耗盡資源。JBoss 透過 instance cache 的老化政策來處理這件事,相關參數集中在 standardjboss.xml。
打開 JBoss 設定目錄下的 standardjboss.xml,找到 container-name 為 Standard Stateful SessionBean 的容器設定。
<container-cache-conf>
<cache-policy>
org.jboss.ejb.plugins.LRUStatefulContextCachePolicy
</cache-policy>
<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>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>
StatefulSessionFilePersistenceManager,也就是序列化到檔案)並從記憶體中移除。JBoss 預設值為 600 秒,可依需求調整。<container-configuration>
<container-name>Standard Stateful SessionBean</container-name>
<call-logging>false</call-logging>
<invoker-proxy-binding-name>stateful-rmi-invoker</invoker-proxy-binding-name>
<container-interceptors>
<interceptor>
org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor
</interceptor>
<interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor>
<!-- CMT -->
<interceptor transaction="Container">
org.jboss.ejb.plugins.TxInterceptorCMT
</interceptor>
<interceptor transaction="Container">
org.jboss.ejb.plugins.CallValidationInterceptor
</interceptor>
<interceptor transaction="Container">
org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor
</interceptor>
<!-- BMT -->
<interceptor transaction="Bean">
org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor
</interceptor>
<interceptor transaction="Bean">
org.jboss.ejb.plugins.TxInterceptorBMT
</interceptor>
<interceptor transaction="Bean">
org.jboss.ejb.plugins.CallValidationInterceptor
</interceptor>
<interceptor>
org.jboss.resource.connectionmanager.CachedConnectionInterceptor
</interceptor>
<interceptor>org.jboss.ejb.plugins.SecurityInterceptor</interceptor>
</container-interceptors>
<instance-cache>
org.jboss.ejb.plugins.StatefulSessionInstanceCache
</instance-cache>
<persistence-manager>
org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager
</persistence-manager>
<container-cache-conf>
<cache-policy>
org.jboss.ejb.plugins.LRUStatefulContextCachePolicy
</cache-policy>
<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>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>
<container-pool-conf>
<MaximumSize>100</MaximumSize>
</container-pool-conf>
</container-configuration>
調整時要注意三個參數的相對關係:overager-period 決定檢查的靈敏度,max-bean-age 決定單一實例能閒置多久,而 max-bean-life 則是硬性上限。把 max-bean-age 調大可以減少序列化次數、改善效能,但會佔用更多記憶體;調小則相反。
如果你的有狀態 Bean 會暫存大量資料,除了縮短 max-bean-age,也建議確認 persistence manager 指向的暫存目錄有足夠磁碟空間,並定期清理殘留的序列化檔。