Known Issues for Unwired Server

Not able to register the BlackBerry client applications over WiFi.

BlackBerry applications cannot connect to Unwired Server directly.

Workaround: Request a patch from CS&S, and you must use BlackBerry Enterprise Server (BES) to establish Unwired Server application connections. This is the only mobile channel supported. See Configuring BlackBerry Push Settings in Sybase Control Center online help, BlackBerry Provisioning with BES in System Administration, and Mobile Channel Interfaces in Developer Guide: BlackBerry Object API Applications.

Synchronization fails when QUEUED_MESSAGES.adm file gets too large.

Workaround: Run the Pack Tool utility to defragment and reclaim unused space within tables and memo files that the Advantage Database Server® (ADS) data file uses, and to ensure Unwired Server runs properly. Run this utility as part of an ongoing maintenance program.

See Running the Pack Tool Utility.

Unwired Server stops responding when suspending package subscriptions.

Suspending a large volume (250 to 350 users) of package subscriptions may cause Unwired Server to stop responding.

Workaround: Suspend package subscriptions in batches of 50 users.

Listview object query fails with error.

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. The mlsrv_err.log reports java.lang.OutOfMemoryError.

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.

Deleting an unsynched package causes an error.

If you deploy a package and then delete it before it has been synchronized, and if a device then attempts to synchronize the application, the sync fails since the package no longer exists. However, if you redeploy the package, and the device attempts to synchronize the application, the sync still fails even though the package exists. The server log reports:

YYYY-MM-DD HH:MM:SS.944 ERROR Mobilink Thread-165 [com.sybase.ml.sup.Logger] [-10013] Version 'default_errorhandler.1_0' not found in the ml_script_version table. Cannot synchronize 

Workaround: Restart Unwired Server, and the application successfully syncs the package.

Devices on 3G/4G network not able to connect to Unwired Server.

A connectivity issue may occur between the device and Unwired Server. The current client libraries use a protocol that supports HTTP chunked transfer-encoding only. 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 the communication is done 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 sent back to the server indicating that the device is online.

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

Enabling compression incurs additional processing on the device and the server side to optimize the amount of data to be transferred over the network.

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.

Adding synchronization parameters or personalization keys to a deployed package using the UPDATE deployment method may render client applications based on the previous package model version nonfunctional.

Workaround: None.

Existing client code not retrieving records.

Existing client code does not retrieve any records after you add sync parameters, and re-deploy the client.

Workaround: Update the MBO, and regenerate the code. Add the syncparamClass.save() method in the client code.

Adding new operations onto a mobile business object in a deployed package using the UPDATE deployment method may render client applications based on the previous package model version, nonfunctional.

Workaround: None.

Unwired Platform data must be periodically manually transferred to System Landscape Directory (SLD).

Workaround: Schedule the batch files, runXMLgenerator.bat and sendPayload.bat, to send periodic updates into the SLD, located in UnwiredPlatform_InstallDir\Servers\UnwiredServer\SLD\. See Registering Sybase Unwired Platform with System Landscape Directory in System Administration.

Even though a domain is disabled, messaging clients continue to receive messages from server.

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

The full range of valid values is not supported if the attribute uses the default datatype (int) for a SQL Anywhere® database column of type unsigned int.

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.