SAP Knowledge Base Article - Preview

1928774 - SUP Android sync fails via RelayServer using HTTPS

Symptom

  • Synchronization problem when connecting to Sybase Unwired Platform (SUP) server through a Relay Server using HTTPS on port 443. The Android app does successfully register but when trying to synchronize the following SynchronizationException is thrown:

    10-16 17:32:29.368: W/System.err(30465):
    com.sybase.persistence.SynchronizeException:
    com.ianywhere.ultralitejni12.implementation.JniException: UltraLiteJ
    Error[-1305]: MobiLink communication error -- code: 24, parameter: ,
    system code: 336134278Details:
    10-16 17:32:29.368: W/System.err(30465): StreamErrorCode = 24
    10-16 17:32:29.378: W/System.err(30465): StreamErrorMessage = null
    10-16 17:32:29.378: W/System.err(30465): at
    com.sybase.sup.client.persistence.RbsDatabaseDelegate.internalSynchronize
    (RbsDatabaseDelegate.java:807)
  • MobiLink error 24 stands for SECURE_CERTIFICATE_NOT_TRUSTED
    http://dcx.sybase.com/index.html#1201/en/saerrors/mlcommerr24.html
  • This has been tested on Android device running Android 4.0.4 and also in Android Emulator running Android 2.2.
  • SUP Libraries (.jar files) are taken from SUP Mobile SDK 2.1.3
  • The same settings for Relay Server (HTTPS, ports 443) are working correctly with BlackBerry version of this app


Read more...

Environment

  • Sybase Unwired Platform 2.x
  • Android 2.x, 3.x and 4.x devices
  • HTTPS via Relay Server

Product

Sybase Unwired Platform 1.5.2

Keywords

KBA , MOB-SUP-SDK-OAP , Mobile SDK Object API , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.