• 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: Async HTTP stream never gets called n 10.2
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Async HTTP stream never gets called n 10.2


  • Subject: Re: Async HTTP stream never gets called n 10.2
  • From: Becky Willrich <email@hidden>
  • Date: Wed, 16 Feb 2005 11:23:14 -0800

Yup; the run loop's running. The only other thing I can think of off the top of my head is that you've inadvertently scheduled on the wrong run loop, but that would mean your program's threaded and you're executing on an unexpected thread. You could try printing out the return value of CFRunLoopGetCurrent() and make sure it's the same value each time through. You can also try doing a tcpdump to see how much (if any) of the failing transaction gets through. If the new request isn't even being transmitted, you probably have some kind of a run loop scheduling problem - scheduled on the wrong run loop, run loop isn't running or is running in the wrong mode, etc. In the unlikely event that the bug's on the server side, you'll see that, too - no bytes coming back from the server. FWIW, I don't know of any bugs in 10.2 CFNetwork that would account for this kind of a failure - first several transmissions work fine, but a later one does not.

Are all the requests going to the same host? Are you using persistent connections? Is there a proxy configured? What other properties are set on the streams? Is there anything unusual about the requests you're transmitting - do they carry especially large bodies, or do the headers or the URL contain high-bit characters? We really need a lot more information to be able to guess what's going wrong....

REW


On Feb 16, 2005, at 11:08 AM, Miro Jurišić wrote:

One possibility is that the run loop is no longer running; that will certainly stop events from flowing. - REW

Well, I am in the main thread, and when this happens I can interact with the app (it's not beachballed), so Carbon Events are flowing normally. This indicates that the run loop is running, right?


meeroh

--

<http://web.meeroh.org/> | KB1FMP

"And when I have understanding of computers, I shall be
        the supreme being!" -- Evil, "Time Bandits"



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Async HTTP stream never gets called on 10.2
      • From: Miro Jurišić <email@hidden>
References: 
 >Async HTTP stream never gets called n 10.2 (From: Miro Jurišić <email@hidden>)
 >Re: Async HTTP stream never gets called n 10.2 (From: Becky Willrich <email@hidden>)
 >Re: Async HTTP stream never gets called n 10.2 (From: Miro Jurišić <email@hidden>)

  • Prev by Date: Re: Async HTTP stream never gets called n 10.2
  • Next by Date: Re: Async HTTP stream never gets called on 10.2
  • Previous by thread: Re: Async HTTP stream never gets called n 10.2
  • Next by thread: Re: Async HTTP stream never gets called on 10.2
  • Index(es):
    • Date
    • Thread