title: NSURLConnection getting limited to a Single Connection at a time?
body: <p>OK - let's rephrase this whole question shall we?</p>
  
  <p>Is there any way to tell if iOS is holding onto an NSURLConnection after it has finished &amp; returned it's data?</p>
  
  <p>I've got 2 NSURLConnections I'm instantiating &amp; calling into a server with. The first one initiates the connection with the server and then goes into a COMET style long-polling wait while another user interacts with the request.  The second one goes into the server and triggers a cancel mechanism which safely ends the first request and causes both to return successfully with a "Cancelled by you" message.</p>
  
  <p>In the happy path case the Cancel button will never be clicked. But it's possible to click it and exit the current action.</p>
  
  <p>This whole scenario works GREAT once. And then never works again (until the app is reset).</p>
  
  <p>It's as though the first time thru one of the connections is never released and we are from then on limited to only a single connection because one of them is locked.</p>
  
  <hr>
  
  <p>BTW I've tried NSURLConnection, AFNetwork, MKNetworkKit, ASIHTTPRequest - no luck what-so-ever with any other frameworks. NSURLConnection should do what I want. It's just ... not letting go of one of my connections.</p>