In our efforts to make things as O-O as possible, we are using one table per SDO, and all logic accessing that table is encapsulted in the associated SDO. Since a procedure/function in one SDO sometimes needs to access data in another SDO in a non-SmartContainer environment, we have one SDO (we'll call it SDO-A) run the other SDO (which we'll call SDO-B) persistently and add SDO-B to the SDO-A's super procedure stack. When the instance of SDO-A is destoyed, it needs to destroy SDO-B that it started. We've tried to do this by overriding the destroyObject procedure in SDO-A to first remove SDO-B from it's super procedure stack and run destroyObject in SDO-B before running it's own super destroyObject procedure (RUN SUPER).
All goes well, except that SDO-B is still running on the stateless AppServer partition. No connections are bound, but the persitent SDO-B is still running on the AppServer, taking up memory on that machine.
Has anyone out there had experience running one SDO from another in a non-SmartContainer environment, and if so, been able to succesfully delete the 2nd SDO from the AppServer partition when deleting the first SDO?
All goes well, except that SDO-B is still running on the stateless AppServer partition. No connections are bound, but the persitent SDO-B is still running on the AppServer, taking up memory on that machine.
Has anyone out there had experience running one SDO from another in a non-SmartContainer environment, and if so, been able to succesfully delete the 2nd SDO from the AppServer partition when deleting the first SDO?