BlackBerry MDS Integration Service issues fixed in this release
The BlackBerry® MDS Integration Service did not publish browser-pushed applications successfully to BlackBerry devices and
users could not install the applications. (297136)
If the time on the BlackBerry® MDS Application Console differed from the time on the computer that hosts the BlackBerry MDS
Integration Service, the BlackBerry MDS Integration Service might not push applications to BlackBerry devices when you expected
it to. (277254)
In certain circumstances, the BlackBerry MDS Integration Service stopped responding shortly after starting because the
BlackBerry MDS Integration Service pool experienced a failure and could not failover successfully. (SDR 263253)
When you ran the mdsis-cluster-failure-recovery.bat tool after the BlackBerry MDS Integration Service pool stopped responding,
the tool did not update the BlackBerry MDS Integration Service database and displayed the following error: "Exception in thread
"main" java.lang.NoClassDefFoundError: Could not initialize class net.rim.wica.ag.base.log.AGLog." (DPI225937)
If you prefixed log file names with double-byte characters, the log file name for BlackBerry MDS Integration Service was corrupted.
(DPI 225264)
You could install a signed application on BlackBerry devices without adding the certificate to the BlackBerry MDS Integration
Service if you scheduled the application installation to occur while the BlackBerry MDS Integration Service was configured to
allow unsigned applications. (DPI 223758)
You could not log in to the BlackBerry MDS Application Console if the BlackBerry Configuration Database was configured for
database mirroring and failed over using a non-default port number (1345). (DPI 223730)
In certain circumstances, after the BlackBerry® Enterprise Server failed over, the BlackBerry MDS Integration Service could not
connect to the BlackBerry MDS Connection Service. As a result, you could not manage or install BlackBerry MDS Runtime
Application Applications on BlackBerry devices, and users could not search for BlackBerry® MDS Runtime Applications using
the BlackBerry® MDS Control Center on the BlackBerry device. (DPI 223697)
If you installed the BlackBerry MDS Integration Service with a BlackBerry Enterprise Server environment that supported high
availability, and you selected support for database mirroring and the dynamic port type during the install, the BlackBerry MDS
Integration Service did not start when the setup application completed. (DPI 223298)
When a user requested a list of available applications using the BlackBerry MDS Control Center on the BlackBerry device, if the
application list that the BlackBerry MDS Integration Service sent to the BlackBerry MDS Connection Service was close in size to
the maximum data amount permitted per connection that you configured for the BlackBerry MDS Connection Service, the
BlackBerry MDS Connection Service might not have accepted the application list. (DPI 222584)
If you stopped the BlackBerry Configuration Database, the BlackBerry MDS Integration Service services did not stop. (DPI 222151)
In the BlackBerry MDS Application Console, if you switched between the user management page and the device management
page multiple times in quick succession, the pages did not refresh correctly, and might have displayed incorrect user or device
information. (DPI 222132)
On Windows Server® 2008 operating systems, in certain circumstances, a stack trace appeared in the BlackBerry MDS Integration
Service log file when the BlackBerry MDS Runtime on BlackBerry devices tried to activate with the BlackBerry MDS Integration
Service, and the BlackBerry MDS Runtime did not activate successfully. (DPI 222082)
If the BlackBerry MDS Integration Service received a response from a web service with empty or null strings in a string array, the
Release Notes
BlackBerry MDS Integration Service issues fixed in this release
14
Commentaires sur ces manuels