Hi !
> Passivation should definitely not kill a stateful session
> bean. (Does JBoss
> do this?
No. JBoss doesn't 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.
JBoss 2.4 and greater has a configurable timeout for this purpose.
> > Right now it seems once passivation occurs on the stateful bean the
> session
> > dissapears into a black hole, and when the server tries to
> activate it it
> > blows. Surely this is not correct behaviour on part of the
> server? And
> this
> > is what I am trying to fix.
This is strange. Do you have (in the stateful) a reference to an entity bean
that is deleted from other EJBs after passivation of the stateful ?
Simon
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
