Known Issues for Unwired Server

The support agreement between Oracle and SAP is no longer in effect as of December 31, 2013.

Workaround: See SAP Note 1949332 for workaround and additional instructions.

If your Unwired Server service startup is set to manual, the Unwired server will fail to start the first time you start SAP Mobile Server service from the Windows Services panel directly after the upgrade.

Workaround: Restart the Unwired Server from the desktop shortcut.

If the key store and keypair passwords do not match, you are unable to save the certificate alias, and receive the following error message:

Save failed. Cannot recover key.

Workaround: From the SCC console, select Monitoring, and click Purge in the right panel. Enter the proper time range for the purge and click OK to execute the purge operation. The monitoring log is purged within the specified time range. Alternatively, use SUPCluster.deleteMonitoringData() to clean up monitoring data. See Developer Guide for Unwired Server Runtime, Management API for additional details.

If domain or package is deleted in cluster during one server stopped, some PropertiesNotFoundException error messages can be found in server log when starting the server node. These messages are harmless, and will not affect any functionalities.

Workaround: No action is needed.

Could Not Find SUP_HOME\Servers\UnwiredServer\bin\..smp_server.lock

Workaround: None. This error has no impact.

For a composite operation, if the name of a child MBO in the composite relationship begins with lower case, deployment would fail. 

Workaround: Change the first character of the child MBO's name to upper case using Unwired WorkSpace.

While the MBO developer can modify the MBO attribute default value for a deployed package, and redeploy the package to Unwired Server in Update mode without an error or warning, the new default value does not take effect.

Workaround: Use Replace mode to update the MBO default setting.

When stopping the Windows service for Unwired Server, very infrequently the process hangs. This problem is independent of the means used to stop the service.

Workaround: See Process of Stopping Unwired Server Service Hangs.

You can still upload BTX to the configured Solution Manager server, even if you have not enabled end-to-end tracing for an application connection.

Workaround: None.

Due to an issue with SySAM licensing 64-bit operating systems running in a zh_CN locale result in characters appearing incorrectly.

Workaround: None.

Workaround: Either:

Workaround: None. Look for deployment errors in the domain log.

If a Create operation succeeds at the enterprise information system (EIS), but its corresponding Entity Read operation fails, the EIS is updated but the cache database (CDB) is not. Error information may be reported in the Unwired Server log, but the error is not propagated to the device client. LogRecord shows 0 (zero), but findAll does not show the new record on the device.

Workaround: None. The change appears in the CDB and the device when the CDB is refreshed (for example, when the cache interval expires).

LDAP role/authentication search base cannot support special characters.

The following characters have special meaning when they appear in a name in LDAP: , (comma), = (equal sign), + (plus sign), < (less than), > (greater than), # (number sign), ; (semicolon), \ (backslash), and " (quotation mark).

LDAP providers do not currently handle these special characters in any names or DNs, including username, DefaultSearchBase, AuthenticationSearchBase, RoleSearchBase, AuthenticationFilter, and RoleFilter.

Workaround: None.

Workaround: After deployment, adjust the "onDemand" coherence window from Sybase Control Center.

A 32-bit Unwired Server is not supported when you are developing messaging applications that process large messages. 32-bit servers run into memory issues and can potentially further result in incorrect data synchronizing with the Unwired Server cache.

Workaround: Install Unwired Platform runtime components on 64-bit hosts.

Unwired Platform no longer allows composite orphans, that is MBO child entities within a composite relationship that have no parent entity. Depending on the system configuration, the upgrade may physically delete the orphans, or may only logically delete them, then physically delete them during a subsequent cache purge process. Either way, applications that use MBOs with composite orphans may not behave as expected after migration.

Additional Information on Composite Orphans

An example of a scenario in which parentless child entities can occur is a two MBO parent-child model integrated with JDBC for sales orders and line items. If the data model specifies that line items are inserted first, the application attempts to load child line items for a sales order that does not yet exist. Those line items disappear from the cache before the application can load the parent sales order.

When performing a listview object query with very large data sets, the client returns an error code 571 or 1053, and the server becomes temporarily unavailable, or tries to restart.

Workaround: Modify the maximum Java heap size to handle very large amounts of data in an object query. See Configuring Unwired Server Performance Properties in System Administration.

A connectivity issue may occur between the device and Unwired Server. The current client libraries use a protocol that support only HTTP chunked transfer-encoding. 3G/4G traffic might, in some cases, be subject to content filtering and convert the messages from chunked transfer-encoding to fixed content-length if communication is via standard HTTP ports, which most commonly are 80 and 8080. Since the client application can support only chunked transfer-encoding, the communication cannot be established. In effect, a response cannot be returned to the server indicating that the device is online.

Workaround: Use a nonstandard HTTP port (any port other than 80 or 8080) or an HTTPS port, that is, 443 for Unwired Server client communication from devices to the Relay Server or external load balancer, whichever one is used, in the DMZ.

Workaround: Carefully evaluate whether the compression trade-off is appropriate in the deployment environment, and carefully size the server capacity to support it. If appropriate in a particular environment, follow the Sybase Unwired Platform Developer Guides to enable compression.

Workaround: None.

Workaround: To disable any outbound activity to a client, lock the application connection associated with that client.

Workaround: To support the full range of valid values for an unsigned int attribute in the EIS, set the datatype for the corresponding MBO attribute as long.