Yeah, that's not going to work. SocketClientInvoker wants to talk to a SocketServerInvoker. For example, in Remoting versions 2.0.0 and above, each invocation and each response is preceded by a version byte. For another, the client will try to create an ObjectInputStream, which means the server has to create a matching ObjectOutputStream.
Basically, you'd have to make your server code look sufficiantly like a SocketSereverInovker to satisfy the SocketClientInvoker.