java - Stateful EJB not being passivated when the client VM is abruptly terminated -


i have stateful session bean deployed on jboss 4.3 following config on jboss.xml:

<cache-config>       <idle-timeout-seconds>7200</idle-timeout-seconds>       <remove-timeout-seconds>8000</remove-timeout-seconds> </cache-config> 

ie:

the bean should passivated after 2 hours of idle , removed after 2 hours , 15 minutes.

the problem is: when client vm abruptly terminated bean neither passivated nor removed.

is there way avoid this?

a container may passivate stateful session bean instance when instance not in transaction.

a container must not passivate stateful session bean extended persistence context unless following conditions met:

  • all entities in persistence context serializable.
  • the entitymanager serializable.

any interceptor classes associated stateful session bean must serializable.

the references can possibly restrict bean getting passivated.


Comments

Popular posts from this blog

jQuery Ajax Render Fragments OR Whole Page -

javascript - Iterate over array and calculate average values of array-parts -

ASP.NET Javascript: window.open won't work twice -