I am getting very weird behavior. My client calls into a remote object. That remote object then calls back on an object being served by the client (and all registered clients who are also serving the same callback object).
When the server's remote object goes to call back on the client's callback object (in this case there is just one client), the method call results in an exception (see below). Yet despite the exception the call succeeds behind the scenes anyway. I don't understand how that is possible? Furthermore, weirdly the exception message gets called, and then the console.print that comes right after the method call gets executed. I guess this is because the actual exception is being handled on a different thread. Either way, this is spooky behavior. yeah it works, but why am I getting this message? The exact exception message is: "No connection could be made because the target machine actively refused it" =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
