We use sqlj in server side to retreive and update data in Oracle 8. Some stateful session bean are designed to hold the sqlj DefaultContext and call sqlj. The problem is: while the container try to passivate these stateful session bean, it failed because the StatefulSessionbeanFilePersistencemanager can not passivate the DafaultContext, so does it while container tries to activate them. I am wondering what caused these problem? The code or the MBean in jboss deployment descriptor?
Is DefaultContext truly serializable? I suggest testing it. It it is not, you will have to make the variable transient, and reinstate the value during activation.