Hi !

> Q1
> ----
> When I checked what was happening during passivation of the 
> SFSB I was using 
> readObject() and writeObject() to serialize the handles of of 
> any referenced 
> entity beans.  A handle was obtained from an EB's remote 
> interfaces via 
> EJBObject.getHandle().  The fix was to instead serialize both 
> an EB's home 
> and primary key via EJBObject.getEJBHome() and 
> EJBObject.getPrimaryKey().
> 
> Why does this work?  I thought that we were supposed to use 
> the handle to 
> pass EB references around.  
> What exactly should be saved to properly and portably restore the EB 
> reference?
> And does it make a difference if the reference is being 
> passed to a real 
> remote client instead of another bean (I would hope not)?

Well, if I remember well EJB spec already takes care of this, you should not
do anything :)

> Q2
> ----
> So JBoss is correctly passivating SFSBs once the 
> <max-bean-age> is reached, 
> and will activate them correctly (if I don't screw it up) 
> when later needed.  
> How then does JBoss know when to finally kill off a bean (eg. 
> where the 
> client has died)?  Is there a way to configure this?

As I've already specified twice, in JBoss 2.4 there is a new tag
<max-bean-life> for this purpose

Simon

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

Reply via email to