You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running send notification in a tight loop to try and benchmark the
performance/throughput. I'm
seeing a broken pipe exception fairly often. This limits my throughput to
around 100-300
messages per second, with significant overhead in re-establishing the
connection. I've enabled
TCP keepalive, but this doesn't seem to have effected performance at all.
Original issue reported on code.google.com by str...@gmail.com on 1 Dec 2009 at 4:38
The text was updated successfully, but these errors were encountered:
Solved in 2.0. The new javapns.notification.transmission.NotificationThread
class provides the ability to limit and manage automatically the number of
notifications per connection, to avoid this issue with Apple servers.
Original comment by sype...@gmail.com on 9 Sep 2011 at 7:03
Original issue reported on code.google.com by
str...@gmail.com
on 1 Dec 2009 at 4:38The text was updated successfully, but these errors were encountered: