Stateful passivation problem (serialization)

[eganallen]

I have an instance variable jndiContext of type Context that is assigned new InitialContext() in the setSessionContext() method in my stateful session EJBs. I realize that javax.naming.Context is not serializable but I understood that the container (as per the EJB1.1/2.0 spec) should still be able to deal with this instance variable given it is of javax.naming.Conext (and thus, javax.naming.InitialContext) and NOT hinder passivation.

Here is server.log info:

[Bean Cache] Scheduling for passivation overaged bean LineageManagerEJB with id = 1012776007792 - Cache size = 1
[Bean Cache] Aging out from cache bean LineageManagerEJBwith id = 1012776007792; cache size = 1
[Container factory] Scheduled passivation of bean LineageManagerEJB with id = 1012776007792
[Container factory] java.rmi.ServerException: Could not passivate; nested exception is:
[Container factory] java.io.NotSerializableException: javax.naming.InitialContext
[Container factory] java.io.NotSerializableException: javax.naming.InitialContext
[Container factory] at java.io.ObjectOutputStream.outputObject(Unknown Source)
[Container factory] at java.io.ObjectOutputStream.writeObject(Unknown Source)
[Container factory] at java.io.ObjectOutputStream.outputClassFields(Unknown Source)
[Container factory] at java.io.ObjectOutputStream.defaultWriteObject(Unknown Source)
[Container factory] at java.io.ObjectOutputStream.outputObject(Unknown Source)
[Container factory] at java.io.ObjectOutputStream.writeObject(Unknown Source)
[Container factory] at org.jboss.ejb.plugins.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager.java:285)
[Container factory] at org.jboss.ejb.plugins.StatefulSessionInstanceCache.passivate(StatefulSessionInstanceCache.java:67)
[Container factory] at org.jboss.ejb.plugins.AbstractInstanceCache$1.execute(AbstractInstanceCache.java:709)
[Container factory] at org.jboss.util.WorkerQueue$QueueLoop.run(WorkerQueue.java:199)
[Container factory] at java.lang.Thread.run(Unknown Source)

Help!!
thanks,
Egan Allen

[armint]

You appear to be correct. In EJB2.0 spec section 7.4.1:

If the session bean instance stores in its conversational state an object reference to the
java:comp/env JNDI context or its subcontext, the container must be able to save and restore the
object reference across the instance’s passivation. The container can replace the original object with a
different and functionally equivalent object during activation.

This looks like a bug. Perhaps, you should submit it to http://sourceforge.net/tracker/?func=add&group_id=22866&atid=376685