A fundamental relationship exists between BlackBerry server software and Java Runtime Engine software. This relationship specifically relates to the BlackBerry MDS Connection Service. This becomes very apparent if ever on the related server you update Java to a current version and remove the older version(s). Now Java does this cleanup of older versions automatically with the introduction of Java version 6.10. Without the correct pointer to the latest changed Java version, the BlackBerry MDS Connection Service will become effectively broken. The pointer is a registry entry that refers to the associated jvm.dll file of a version of Java you have installed. Note – if you have multiple versions of Java then you have multiple jvm.dll files on your system.
It’s been a little while since I originally posted on this; in fact, since then RIM has introduced some new server products that are basically all the same code foundation. This means that the same solution still applies wherever MDS is involved. Perhaps in the future RIM will find a way to automatically make the adjustment, but for now you will have to do the steps yourself. The nice thing, as you will see below, is that Java may help by using a consistent path with updates of the same version.
The path to the Java jvm.dll file has been changed; the new path is:
Use this link to the previous article for the outline of the registry editing steps involved: