Michael Jara wrote:
Passivation should definitely not kill a stateful session bean.  (Does JBoss
do this?  So far, I haven't deployed anything in JBoss that is idle for that
long a period.)  However, I wouldn't be surprised if JBoss periodically
aged-out unused stateful session beans.  I think that most good app servers
will do this to clean up after clients which have died, or have not politely
disconnected.
Don't have original message, but it could be that passivation is not working correctly (there are bean references etc. in passivated bean) and after that bean can not be activated again and things go bad.. that is what happened to me.

--
    jK.MkIII
 
 
  _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to