Intermittent error and missing notifications: Error: Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Send one notification to 9 different devices
2.
3.

What is the expected output? What do you see instead?
All notifications are delivered.

What version of the product are you using? On what operating system?
Not sure.  I downloaded the latest version about 2 months ago in Oct 2010.
Windows Server 2008 Standard.  W2k3 R2.  This repros on two different machines.

Please provide any additional information below.
I noticed at least one notification is missing on the device.  The missing 
notification was queued successfully and success callback is called for that 
missing notification.

I am getting this intermittent errors:
Error: Unable to write data to the transport connection: An established 
connection was aborted by the software in your host machine.

But if I change the logic to send to only that problematic device, it works 
fine.  

Original issue reported on code.google.com by chang....@gmail.com on 15 Dec 2010 at 2:54

[GoogleCodeExporter]

Do I have to sleep between queueing of each notifications?  I noticed the test 
example sleep for 15 seconds.

Original comment by chang....@gmail.com on 15 Dec 2010 at 2:56

[GoogleCodeExporter]

You could be sending a bad device token or otherwise malformed notification if 
this happens...

Original comment by jond...@gmail.com on 15 Dec 2010 at 3:36

[GoogleCodeExporter]

Hi, Thanks for the reply.  I double check the device token and notification 
fields and they are correct.  The successful call back 
service_NotificationSuccess() is called.  I changed the logic to send out only 
one notification and it works fine.  But when I send out a batch including the 
same notification I just sent, the same notification didn't get sent and got 
the above error.

Original comment by chang....@gmail.com on 17 Dec 2010 at 7:56

[GoogleCodeExporter]

Just because the NotificationSuccess is called, unfortunately does not 
conclusively mean that it was sent...

You'll need to do some debugging and see which message is failing, then dissect 
why exactly (in terms of looking at the bytes and comparing them to the apple 
spec) what's wrong with the message (assuming you're getting a disconnection 
after this message).

Original comment by jond...@gmail.com on 14 Feb 2011 at 7:39

• Changed state: Invalid

[GoogleCodeExporter]

i am facing the same issue, i get that error message back.. 
did anyone find a solution?

Original comment by i...@izzygoldstein.com on 22 Apr 2013 at 11:21

[GoogleCodeExporter]

Same happens to me... only get's this error in batch sending. otherwise 
everything works fine.

Original comment by pbr...@wingman.pt on 10 Jan 2014 at 8:44