List of Known Issues for Unwired Server

When you run Unwired Server in a cluster environment, the cache serves the latest data from the backend EIS system instead of the data in the cache.

Workaround: None.

An MBO with filters will not receive any push sync using DCNL.

Workaround:Place the custom filter classes in a jar file and put the jar file in the Servers\UnwiredServer\lib directory so the classes are picked up by the system class loader. This file must be copied to other nodes in the cluster whenever it changes.

If you use a remote desktop from a Windows 2000 machine and connect to a machine that starts dblsn.exe, you may get an exception and the Remote Desktop application will close.

Workaround: Do not to use a remote desktop on a Windows 2000 machine and then connect to a machine with Sybase Unwired Platform installed that starts the push listener (dblsn.exe).

If you change the URL suffix value to point to a different cluster name, the suffix is not automatically updated when you test the file-based mobile business object. This is because the suffix is cached as part of an on-device profile, which typically does not change.

Workaround: To update the URL suffix in the on-device profile, clear the remote database on the client device and synchronize the mobile business object again.

If that does not work, uninstalling the Sybase Unwired Platform client and re-installing should clean up the cache files.

• For Blackberry, in JDE, use the Erasing simulator file option to clear the cache.
• For Win32, delete the database files, *.udb, *.~db.

When you are using the Sybase Relay Server Hosting Service and a cluster with multiple Unwired Server installations, the relay server outbound enabler (RSOE) on the slave server crashes when you deploy an MBO.

Workaround:

1. Restart the primary server. This should fix the problem. If it does not, continue to the next step.
2. From the primary server, copy <Install Directory>\Servers\UnwiredServer\tomcat\webapps\ROOT\clusterdata.<version>.zip to the same location on the slave server.
3. On the slave server:
   
   1. Shut down the server.
   2. In a text editor, open <Install Directory>\Servers\UnwiredServer\sup.properties, and set cluster.version to the new version number.
   3. In a command window, run:

      updateFiles
      updateProps -r

   4. Restart the server.

Projects with 20 or more MBOs may take more than three minutes to deploy to Unwired Server.

Workaround: Deploying from the command line is a little faster. See Creating and Deploying a Package from the Command Line.

If SA or ASE smalldatetime, datetime, timestamp, and time column types are used as MBO attributes, then update operations may fail due to the where clause included for concurrency control check in the generated SQL. And a create operation may not return the same precision as inserted. This is because milliseconds and seconds are ignored for these types.

Workaround: After creating the MBO, manually remove the fields of smalldatetime, datetime, timestamp, and time column types from the where clause (used for concurrency control check) in the generated SQL query of the update operation. And for a create operation, ignore entering the seconds and milliseconds precision.