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.
02-01-2013 08:55 AM
It would seem it is definitely environmental, you would need to investigate further on your side. It could be firewall related or an issue with the server, tough to say. But as it works from your other server it should be safe to assume your service is working as expected and the SDK, if set up the same, is also configured correctly.
02-01-2013 09:02 AM
Thanks. Will check and let you know.
But can you please guide me as to why and when do we get this scokettimeoutexception.
02-01-2013 09:05 AM
It's a standard Java error, usually means the connection timed out when waiting for data from a read, or when trying to establish the connection.
02-01-2013 11:55 AM
I tried to access: https://cp476.pushapi.na.blackberry.com/mss/PD_pus
02-04-2013 12:31 PM
I used the Push Service SDK to send a request to the URL you mentioned. Of course I don't have your password so the request was failed by the RIM push server saying it was unathorized but that was enough to prove that I can attempt to push to your URL.
02-04-2013 11:44 PM
Hi marco ,
We figured out the problem. There is some issue with the firewall on the production server, we are in process of figuring it out.
02-14-2013 05:30 AM
We tried opening the firewall access for the push request url, but still getting the same response.
The network team at our end wants to know the ip and port at which the request is being sent. Can you please tell us your ip and port so that it could be bypassed from the firewall.
We have opened the firewall for ip: 188.8.131.52and ports 80 and 8443.