Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
09-14-2009 09:11 AM
I'm having a problem with push messages getting down to phones in a timely manner and not sure what the cause could be...The app is pushing critical messages down through our MDS push server to a couple of test phones - one is a curve on 4.5 and one is a Storm running 4.7. I'm pushing the messages with the following headers from a .NET WCF Service:
req.Method = "POST";
For now I am stuck using TRANSPORT reliability mode because the BES admins haven't opened up a reliable push port for me to use and I'm wondering if that is part of the problem. The POST to the MDS server is happening within 1 second of me receiving my event from another source, but it takes, on average, 5-10 minutes for the push to reach the phone. These messages are critical and, ideally, must be delivered to the phone within 5 seconds - with about 15 seconds being the maximum acceptable time limit.
The push URL is using the PIN as the delivery address, not the email address.
What is the standard time for delivery of push messages?
Does application vs. transport reliability mode have any bearing on how quickly the messages are delivered?
09-14-2009 12:20 PM
So I think this might be because I was specifying a NotifyURL that wasn't a valid URL (it was leftover from the httppushdemo sample code)...My guess is that the MDS server was trying to notify of delivery and not doing so asynchronously so it would wait until that timed out until it sent the next message. This would explain why it appeared the first push message would come through quickly, then each one from that point one was really slow. Taking out that header appears to have sped things up, though I'm going to need to test more to be sure.
Anyone know how the MDS push server handles the notification and if it does indeed block further push messages, maybe only from the same host, while it waits to notify of the delivery of the previous message?
I'm rockin the BlackBerry DTEK60, Passport, Z30, Z10, Q10, BlackBerry Mini Stereo Speaker, 64 gig PlayBook,BT Headset HS-700
09-21-2009 02:21 PM
BESAdmin's, please make a signature with your BES environment info.
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V
10-08-2009 03:39 PM
Same problem here! i think i'm the only one who got this problem.
When i send rim/pap push to MDS it happening instantly, but it takes about 2~5 min (same like DingusMcgee)
NotifyURL set to localhost:7778 is it corect?
any help for this problem?