SummaryThis article applies to the following:
|
ProblemWhen performing a push using the application-level reliability mode, the BlackBerry MDS or the BlackBerry MDS Simulator occasionally fails to accept the push and responds with error 400 and the following: The specified delivery method is not possible Summary of CausesThis issue is caused by one of the following:
Cause 1The BlackBerry Enterprise Server or device software version is earlier than 4.0. Note: BlackBerry Enterprise Server and BlackBerry Device Software 4.0 and later use the application-level reliability mode. ResolutionUpgrade the BlackBerry Enterprise Server and device software to version 4.0 or later, or set the Cause 2The user has not used the BlackBerry Browser since BlackBerry MDS was started, or the application did not make an HTTP request and did not set the appropriate headers to inform the BlackBerry MDS of its abilities. ResolutionRequest a web page using the BlackBerry Browser, or configure your application to make an HTTP request with required headers. For more information, see this article. Note: BlackBerry MDS does not recognize if the BlackBerry device supports the application-level reliability mode until it makes an HTTP request with appropriate headers. Until this has occurred, BlackBerry MDS assumes it does not make an HTTP request and returns the error. Cause 3The ResolutionConfigure the BlackBerry MDS or MDS Simulator with ports used with the application-level reliability mode. To do so, open the rimpublic.property file and add a The following example shows an entry that enables port 4000 and 5000 for the application-level reliability mode: push.application.reliable.ports=4000,5000 Note: Ports listed in the above example can still be used with other reliability modes or without any reliability mode. Cause 4The application is not listening for the push connection, or the push and application are not using the same port. ResolutionVerify that the push application is pushing to the port on which the application is listening. Cause 5The application is not using ResolutionUse |