*** I wonder if there is an impact of using following statements every time I pass a message to the upper layer or lower...Definitely.
For example... once a slave has completed the job and needs to pass the results back to the Clients, Slaves will do followingWhy? We've been over this before. You are drastically over-using the Registry here. It is possible to construct systems of this complexity with only one object bound in the Registry, and only one Registry too.
as Slaves are as many as 50.. there will be 50 lookup's every time and is this necessary?No. The clients shouldn't even be in a Registry, and there needn't be more than one Registry in the entire system. It's just a bootstrap mechanism. Don't overuse it.
Can I do this once and use "client" instance to report the result back to clients?Yes.
EJP wrote:Now my program flow is :Look. You have one Registry at the server. You bind the server object into it. Clients register themselves with the server. Ditto slaves if Slaves get references to the clients via that server. Clients get references to slaves ditto if necessary.
I think this will create a clone of the slave in the clients JVM.Not unless you commit the error of re-exporting it that we discussed last month in another thread.
So "compute" method execution may happen at that JVM instead of slave's JVMNo. We've been through this before.
Please clarifyHow many times? We covered all this on 28 September. That's two weeks ago.*
Just a clarification for my Understanding....What* 'clarification'? You were told all about this two weeks ago at some length. Nothing has changed. You're just asking for the same information to be repeated. Over and over again.
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.UnmarshalException: unrecognized method hash: method not supported by remote objectYour stubs and remote interfaces and remote objects aren't up to date in all places. Clean, rebuild, redeploy.