• 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
Asynchronous OTConnect and Timeout
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Asynchronous OTConnect and Timeout


  • Subject: Asynchronous OTConnect and Timeout
  • From: Scott Johnson <email@hidden>
  • Date: Mon, 7 Jun 2004 16:57:41 -0400

Hello,

I inherited an application (CFM Carbon) that is an exhibiting an issue I would like to bounce off people more experienced than I with Open Transport (which is likely most of the people on this list!).

The application is a client of our own server application. The server can be configured as a sole entity or one operating within a cluster. If clustered, my client application will have at hand the IP addresses of the backup servers, should we be unable to contact our designated primary server. (The clustering ability is new and solidifying failover is the task at hand.)

The client application initially sets up an asynchronous TCP endpoint to use to OTConnect to our server. The code has always enforced a short timeout of 10 seconds before we give up and--new with clustering--try the next server in the cluster, if any. The problem is that 10 seconds does not seem to be long enough...I have to allow the client to try to OTConnect to the primary server for around 90 seconds before failing (at which point the client calls OTCloseProvider on that endpoint). Only then, can I attempt to open a new endpoint to a backup server and successfully OTConnect.

Any idea what I may be doing wrong here? Is OTCloseProvider the proper way to sever ties (that never really existed) with the non-functioning server before I move on to the next, or is there something missing?

Apologies if this is a repeat of earlier queries but my search through the archives of this list seemed only to talk about synchronous timeout situations.

Thanks,
Scott

Scott A. Johnson
Software Engineer
Baseview Products, Inc.
email@hidden
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.


  • Prev by Date: OS X SOAP example code
  • Next by Date: Re: OS X SOAP example code
  • Previous by thread: Re: OS X SOAP example code
  • Next by thread: Use CFMessagePort in CFM app?
  • Index(es):
    • Date
    • Thread