• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Distributed Objects & Leopard
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Distributed Objects & Leopard


  • Subject: Re: Distributed Objects & Leopard
  • From: Aurélien Hugelé <email@hidden>
  • Date: Mon, 19 Nov 2007 12:52:22 +0100

Guy, what calls are you using to create the NSSocketPort (i suppose your are using socket port instead of mach port)
initWith??????????, and please give the parameters your are using too.


I had this problem I suceeded to fix.



Aurélien,
Objective Decision Team




On 18 nov. 07, at 22:00, Guy Meyer wrote:

My client server application communicate over sockets using NSConnection.

On the client side, there are multiple threads (not the main thread), communicating with the server.

Each thread has a single NSConnection. The connection is terminated by issuing an invalidate method on the connection and the thread is existed.

On Tiger there is no problem with said architecture.

On Leopard few seconds after the thread being terminated, all other threads (which contains an active NSConnection to the server) receives the following exception (if there are no more threads connected to the same server, the exception does not occur - in this example there 3 threads which receive the exception):

*** NSDistantObject initWithCoder: 0x3 not given away for conn 0x1514bde0
*** -[NSConcretePortCoder decodeInvocation]: no local target
*** NSDistantObject initWithCoder: 0x4 not given away for conn 0x1514f9d0
*** -[NSConcretePortCoder decodeInvocation]: no local target
*** NSDistantObject initWithCoder: 0x2 not given away for conn 0x1515e1f0
*** -[NSConcretePortCoder decodeInvocation]: no local target


I have tried few way to circumvent the issue, like invalidating ports instead of the connection or continuing running the runloop before existing the thread (but as there are are no more input sources the runloop return immediately)

I am looking for ways to terminate the connection without the exception.

Thanks

Guy Meyer




_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Distributed Objects & Leopard
      • From: Guy Meyer <email@hidden>
References: 
 >Distributed Objects & Leopard (From: Guy Meyer <email@hidden>)

  • Prev by Date: Re: Notification when new email received
  • Next by Date: Re: How to know OS Version
  • Previous by thread: Distributed Objects & Leopard
  • Next by thread: Re: Distributed Objects & Leopard
  • Index(es):
    • Date
    • Thread