11-28-2009 03:57 AM
The Widget SDK is my first foray into developing for the BlackBerry.
I've downloaded the installer that bundles the Eclipse IDE (because I was having problems with the Eclipse update) from http://na.blackberry.com/eng/developers/browserdev
I was trying to run the sample (found on http://docs.blackberry.com/en/developers/subcatego
Here's some issues & information:
1. The documentation for this sample seems to assume a standalone MDS and not one as an IDE plug-in - it talks about port 8080 however I found that my instance of the MDS is listening at 28080
2. Acessing localhost at 28080 shows me the MDS status which reports
Build number : 93
Build version : 18.104.22.168
Build Date : 2009/08/12
3. The instructions for the sample say:
Open the rimpublic.property file, which is located in the MDS\config subdirectory of your BlackBerry Email and MDS Services Simulators installation directory. Ensure the "push.application.reliable.ports=100" line is NOT commented out.
I didn't find this line (I found the MDS folder with the file with this name under <Eclipse-Dir>\plugins\net.rim.browser.tools.wcpc_1
4. I'm running Win 7 Ultimate and tried this after allowing MDS access by adding an exception and later by completely disabling the firewall.
5. For the RIM option in the push server code, I get the following exception in the console:
Sending to http://localhost:28080/push?DESTINATION=2100000A&P
java.io.IOException: Server returned HTTP response code: 400 for URL: http://localhost:28080/push?DESTINATION=2100000A&P
6. For PAP, I see:
sending PAP request to http://localhost:28080/pap; pushId = pushID:64424432
Content-Type: application/xml; charset=UTF-8
<!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 2.0//EN"
<push-message push-id="pushID:64424432" ppg-notify-requested-to="http://localhost:7778">
7. On the console for MDS, I see:
<2009-11-28 03:49:48.683 EST>::<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = P apServlet: request from 127.0.0.1 559 bytes...> <2009-11-28 03:49:48.694 EST>::<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = M apping PAP request to push request for pushID:pushID:64424432> <2009-11-28 03:49:48.697 EST>::<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = P ushServlet: POST request from [UNKNOWN @ 127.0.0.1] to [PAPDEST=WAPPUSH%3D210000 0A%253A100%2FTYPE%3DUSER%40rim.net&PORT=100&REQUES
TURI=/]> <2009-11-28 03:49:48.697 EST>::<MDS-CS_MDS>:<DEBUG>:<push id: pushID:644244 32> <2009-11-28 03:49:48.698 EST>::<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = s ubmitting push message with id:pushID:64424432> <2009-11-28 03:49:48.702 EST>::<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = E xecuting push submit command for pushID:pushID:64424432> <2009-11-28 03:49:48.704 EST>::<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = P AP push-id pushID:64424432 returned status code 3007> <2009-11-28 03:52:49.193 EST>::<MDS-CS_MDS>:<DEBUG>:<LAYER = SCM, EVENT = A dmin. Task- refresh media management>
8. After a while, when using PAP, the Eclipse console shows 'Notification connection timeout. Restarting...' and this message keeps repeating.
So if someone could point me in the right direction for getting this to work or give me some idea of what I'm doing wrong, that'd be great! I really don't know too much about BlackBerry development or MDS or push so I'm not sure where to start.
Solved! Go to Solution.
11-29-2009 09:22 AM
First of all, thank you for all of the diagnostic information, that is definitely going to help
Currently we do not support Windows 7 as an official supported OS. However, there were some issues with the push sample that were provided and we have had an update waiting to go up on the web and are awaiting the web site team to publish it. That may be the source of your problems, or Windows 7 may be.
In either case, we will have the Eclipse tooling team take a look at your scenario to see if they can get the corrections to the push sample for you. I know our Team Lead of the Eclipse web development team did make the changes to the push example after he found similar issues. So we should be able to get you going in the right direction.
11-29-2009 02:01 PM
Thank you, I'll keep an out for updates and in the meantime have a go at this on a friends machine with Vista (x86) and see how that works out
Also, just in case someone comes around to this thread again, I forgot to mention earlier, that I'm running the x86 version of Win 7.
12-01-2009 09:19 AM
Turns out that there is a known issue in the MDS connection services where to emulate the push environment you have do a few steps.
Once you have the simulator open, you need to have the device simulator connect through the MDS a couple of times so that it knows that it is actually there.
What we have seen that works, is to open up the browser and go to a link such as http://www.google.com a couple of times and then try the push.
some of our developers have seen that it can sometimes take a few tries in order for the MDS to detect the simulator. We have a bug logged with the MDS team on this topic.
02-25-2010 04:46 PM
Do you know when this bug will be fixed. What if im running an old BES 4.1.6? How would i apply this fix? it seems like i have to make a http connection before each push for mine to work.
02-25-2010 05:26 PM
The bug is in just in the development environment only when testing. On an actual BES it will work just fine. No fix is needed there.