Hi !
> So after 10 minutes of inactivity (jboss's default of 600
> secs) it should be
> passivated --not destroyed.
Right.
> Shouldn't I be able to continue
> to use the bean
> at 12 minutes (upon which the server will de-passify the bean
> ie. activate
> it) without the client ever being aware?
Yes you should.
> And if <max-bean-age> is for passivation where do I specify
> the ultimate
> time after which a very old inactive bean (passivated or not)
> should actually
> be destroyed (eg. dropped connections)?
In JBoss 2.4 and greater there is a <max-bean-life> tag for this purpose.
> Currently it seems that the <max-bean-age> is acting as a
> destroyer and not a
> passivator. Is this understanding correct?
Well, no :)
It should act as a passivator and there are other people on this list
complaining that in JBoss 2.2 (where there was no removal of passivated
states) they create the bean, it gets passivated, they remove it, and since
its state is still present on the filesystem they are able to invoke methods
on a removed bean.
So: try to put in a very simple stateful bean and see if everything works
ok. If not then it's a reproducible bug and you can file in a bug in
sourceforge; otherwise try to add complexity to this simple stateful until
is similar to your real stateful and see at which step things go wrong.
Keep us informed
Simon
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
