
You can either increase the threshold value or you can set it to 0. If you set it to 0, the BlackBerry Controller will
not restart the Lotus Domino server or BlackBerry Messaging Agent when heartbeats are missed. Note that this
workaround can cause problems when heartbeats are missed because of events which affect message flow such
as silent crashes and non-responsive threads.
In some cases, the BlackBerry Enterprise Server marks busy threads as hung and the BlackBerry Controller restarts
the BlackBerry Enterprise Server. (DT 799826)
The BlackBerry Controller does not automatically restart the BlackBerry Enterprise Server after the wait count
threshold is reached on a hung thread. (DT 764171, DT 442654)
Workaround: Run IBM Lotus Domino as an application instead of as a service so that the BlackBerry Controller
only stops the Lotus Domino related processes.
If the BlackBerry Controller creates multiple consecutive dumps on hung threads, the latest dump file overwrites
the previous dump file if the latest file is created in the same minute as the previous dump file; the dump files are
named based on the minute that they are created. (SDR 214488)
BlackBerry Desktop Software known issue
You cannot silently distribute the BlackBerry® Device Software for the BlackBerry® Bold™ 9700 smartphone to
BlackBerry® Desktop Manager 5.0, and you cannot silently distribute the BlackBerry Device Software for the
BlackBerry® Torch™ 9800 smartphone to BlackBerry Desktop Manager 6.0. (DT 1005796)
BlackBerry Dispatcher known issues
If a Wi-Fi® connection is opened between the BlackBerry® Enterprise Server and a BlackBerry device while keys
are being generated, the BlackBerry Enterprise Server may send the device two KEY_ACCEPT packets which leaves
the device without an encryption key. (DT 904881)
Workaround: Users should regenerate the encryption key manually.
If you configure a device to use Wi-Fi connections only, and the device cannot connect to the BlackBerry Router,
the BlackBerry Dispatcher drops the messages that it should be queuing so that the BlackBerry Enterprise Server
can forward the messages to the device when Wi-Fi connectivity returns. (DT 650456)
If two device users swap devices and then failover occurs, the BlackBerry Dispatcher detects duplicate PINs and
resets the PIN to 0 for one of the devices, causing the device to stop functioning. (DT 454394)
Workaround: Restart the standby BlackBerry Dispatcher before the failover occurs, or reactivate the user when
the PIN is reset to 0.
Release Notes
BlackBerry Desktop Software known issue
42
Kommentare zu diesen Handbüchern