A bad recursion-on-error has been observed in ProxyConnection.replaceObject. Under some circumstance, which we didn't record at the time and may now have trouble reproducing, we saw an exception thrown while doing a replaceObject cause a bad recursive invocation of replaceObject in trying to handle the error. To deal with this, we probably need to understand well the error recovery semantics of Java's ObjectOutputStream.