Known Issues for Unwired Server

Workaround: Resolve the issue by performing one of the following:

Workaround: None. Deployment errors are in the domain log.

If a Create operation succeeds at the enterprise information system (EIS) back end, but its corresponding Entity Read operation fails at the back end, the back-end 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 cache database and the device when the CDB is refreshed (for example, when the cache interval expires).

Workaround: Set user name as "supAdmin@admin" in application connection if you set SecurityConfiguration in test code. The user names must match.

Workaround: Reregister the device.

Workaround: None. Works as designed. This is a platform limitation with Android 2.3.3 and Android 3.2.

Workaround: None. There is no impact from this error and it can be ignored.

SELECT   id,
  fname,
  lname,
  address,
  city,
  state,
  zip,
  phone,
  company_name FROM sampledb.dba.customer
WHERE state = :state

Map the Customer MBO state load argument to the state "Propagate to Attribute" from the Load Arguments tab.

LDAP role/authentication search base cannot support special characters.

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

LDAP providers do not currently handle these special characters in any of the 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 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 – 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 the same 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.

Workaround: Regularly run packtool.exe to defragment and reclaim unused space within tables and memo files used by the Advantage Database server.

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.

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 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.

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.

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.