RMI Callback after serialization in Weblogic 10.3

Question

I have an application with a JRE1.6 Swing client and a J2EE server running on weblogic 10.3 (JRE1.6)
For certain operations the server does a RMI Call back to the swing client. So the RMI Object(UpdateListener) is passed to the server during the business call.
public interface UpdateListener extends java.rmi.Remote{
     void update(int action, Object data) throws RemoteException;
My client class implements the this interface to get the CallBack. The problem is that, after reaching the server when i persist and read back the RMI Object from database, i'm unable to do the callback. The stacktrace is
java.rmi.ConnectException: Could not establish a connection with 4079602057493999578C:192.168.7.20R:4131263118401458263S:127.0.0.1:[7001,7001,-1,-1,-1,-1,-1]:domain:Admin_Server, java.rmi.ConnectException: Destination is not a server; No available router to destination; nested exception is:
     java.rmi.ConnectException: Destination is not a server; No available router to destination
     at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:349)
     at weblogic.rjvm.RJVMImpl.getRequestStreamInternal(RJVMImpl.java:609)
     at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:560)
     at weblogic.rjvm.RJVMImpl.getOutboundRequest(RJVMImpl.java:783)
     at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:159)
     at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:211)
     at com.ibsplc.iaviation.utility.realtime.CallBack_1030_WLStub.update(Unknown Source)
When i do the callback before persisting, the callback is working. I thing it is some thing to do with the serialization and WEblogic.
I'm pasting sample code.
//Server method
public void doBusiness(UpdateListener rmiObject, String status) {
     //This call works fine and i get the callback in client
     try {          
          rmiObject.update(0, "Direct CallBack is working");
     }catch(IOException ioe) {
          ioe.printStackTrace();
     //This call doesnot work and i get the exception stacktrace above.
     //This call was working fine in Weblogic 8.1 (JDK1.4)
     try {
          ByteArrayOutputStream byteStream = new ByteArrayOutputStream();
          ObjectOutputStream os = new ObjectOutputStream(byteStream);
          os.flush();
          os.writeObject(rmiObject);
          os.flush();
          byte[] byteArrayOfData = byteStream.toByteArray();
          os.close();
          ObjectInputStream in1 = new ObjectInputStream(new ByteArrayInputStream(byteArrayOfData));
          UpdateListener rmiObjectAfterSerialze = (UpdateListener) in1.readObject();
          System.out.println("Trying call after after serlialze");
          rmiObjectAfterSerialze.update(0, "This call is not working");
     }catch(IOException ioe) {
          ioe.printStackTrace();
Is this something to do with Weblogic10.3? Do i have to do something to reactivate the rmiObject after serialize and deserialize?
I had posted this in core java forum and was suggested to post in weblogic forum.
http://forums.sun.com/thread.jspa?threadID=5436290
Any help is greatly appreciated.
Thanks
Basil

Answer 1

I agree with that and we have removed this kind of callback the new version of the application. But the old version is still being used and had to be recently migrated to weblogic10.3, that is when the issue popped up.
I have made the client implementation class Activatable. The code is pasted below. But still the issue persists. Do i have to do something else after deserialization to activate the stub class?
public class CallBack extends Activatable implements UpdateListener {
    public CallBack(CallBackListener callBackListener) throws RemoteException{
     super(null,0);
    public void update(int activity, Object data) throws java.rmi.RemoteException {
        System.out.println("CallBack Reached");
}