For anyone searching the archives for "connection went invalid while waiting for a reply":
I never found out why this message was appearing, but I found a workaround. Instead of calling [client callbackWithArgument:arg], call [client performSelector:@selector(callbackWithArgument:) withObject:arg afterDelay:0.0] I don't know why this should make a difference! Hamish On Wed, Jul 9, 2008 at 1:11 AM, Hamish Allan <[EMAIL PROTECTED]> wrote: > I'm seeing "connection went invalid while waiting for a reply" in a DO > callback. The client passes self in a call to the server; some time > later, the server calls a method on that client (proxy), the program > hangs for a second or so, the "connection went invalid" connection > appears, but the method call is successful anyway, so it would appear > that the DO machinery is re-connecting everything okay. > > According to the debugger, the message appears as a result of an > uncaught NSException from -[NSConnection sendInvocation:internal:], > called from -[NSDistantObject forwardInvocation]. > > Server and client are both properly retained. > > There seem to be a lot of messages of late on Apple's forums about > problems with iSync (10.5.4) and even Interface Builder (10.5.3, > IB3.1beta6) in which this message is reported. Is it perhaps a bug in > recent versions of the OS rather than in my code? > > Hamish > > P.S. This question has been asked before, but the OP didn't get an > answer (http://www.cocoabuilder.com/archive/message/cocoa/2006/12/29/176458) > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
