Known Issues for SAP Mobile Server

Learn about known issues and apply workarounds for SAP Mobile Server.

Issue #	Description
SMPONP-13039	Oracle support for JDK ended December 31, 2013 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.
SMPONP-10928	Temporary network issues affecting the cluster During some operations, for example, deploying packages after switching a data tier in the Microsoft cluster, or failing to connect to the data tier in a simple cluster, a temporary network issue causes the following warning message to be logged in the server log: 2013-09-04 02:16:05.362 WARN MMS Thread-256 [com.sybase.sup.server.deploy.SupDeployer] [] [] System.Web.Services.Protocols.SoapException: Error sending request to server at Admin.AddTemplate(String strTemplateName, String strTemplateDescription, PropertyItem[] settings) java.lang.RuntimeException: System.Web.Services.Protocols.SoapException: Error sending request to server at Admin.AddTemplate(String strTemplateName, String strTemplateDescription, PropertyItem[] settings) at com.sybase.sup.admin.util.WebServiceUtil.createTemplate(WebServiceUtil.java:219) at com.sybase.sup.admin.util.WebServiceUtil.createTemplate(WebServiceUtil.java:209) at com.sybase.sup.server.deploy.SupDeployer.createTemplate(SupDeployer.java:797) at com.sybase.sup.server.deploy.SupDeployer.saveApplicationInfo(SupDeployer.java:776) at com.sybase.sup.server.deploy.SupDeployer.doDeploy(SupDeployer.java:734) at com.sybase.sup.server.deploy.SupDeployer.deploy(SupDeployer.java:306) at com.sybase.sup.admin.server.DomainAdminImpl.deployWithArgs(DomainAdminImpl.java:365) at com.sybase.sup.admin.server.DOECDomainAdminImpl_DJC.$invoke_0(DOECDomainAdminImpl_DJC.java:384) at com.sybase.sup.admin.server.DOECDomainAdminImpl_DJC.$invoke(DOECDomainAdminImpl_DJC.java:147) at com.sybase.djc.rmi.iiop.server.MessageHandler.processRequest(MessageHandler.java:794) at com.sybase.djc.rmi.iiop.server.MessageHandler.run(MessageHandler.java:306) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:789) Workaround: Redeploy the package after the cluster returns to normal.
SMPONP-9965	Key store and Keypair passwords must match :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: Configure the key store and keypair passwords as follows: While configuring the SAP Mobile Server for mutual SSL, generate the keypair with the same password as the keystore password. For example,if the keystore.jks has password "changeit", the corresponding keypair generated must also have the password "changeit". Save the keystore file. Check for the correctness using the following from the command prompt: `C:\>keytool -list -alias alias_name -keystore keystore.jks -storepass changeit` Restart the services. Set the alias value in the SAP Control Center SSL configuration tab. The save is successful. Restart the server to apply the changes.
SMPONP-8310	SAP Mobile Server experiences significant performance degradation when performing DCN load operations with large DCN request messages when Wily Introscope agents are enabled. Workaround: If not required, remove the Introscope agents from SAP Mobile Server using this command:`C:\SAP\MobilePlatform\Servers\UnwiredServer\bin\configure-introscope-agents.bat -remove`
RTC-302	XML recordings are saved to an incorrect directory. After enabling XML recording in the registry, logs will show that XML recordings are successfully saved to C:\UnwiredServer\logs, which is the incorrect SAP Mobile Platform logging directory. Workaround: Manually add a String Value to the key HKEY_LOCAL_MACHINE\SOFTWARE\Sybase\Sybase Messaging Server\Server (HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sybase\Sybase Messaging Server\Server on 64 bit) with a path relative to the MessagingServer directory (that is, ..\UnwiredServer\logs).
RTC-268	Process of stopping SAP Mobile Server service hangs. When stopping the Windows service for SAP Mobile Server, very infrequently the process hangs. This problem is independent of the means used to stop the service. Workaround: See Process of Stopping SAP Mobile Server Service Hangs.
RTC-238	Update deployment allows definition of a new MBO attribute default, but the new default value does not take effect. While the MBO developer can modify the MBO attribute default value for a deployed package, and redeploy the package to SAP Mobile 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.
RTC-42	Business transaction XML (BTX) uploads when end-to-end tracing is not enabled for an application connection. 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.
RTC-38	Server logs Chinese environments result in garbled characters under certain conditions. Due to an issue with SySAM licensing 64-bit operating systems running in a zh_CN locale result in characters appearing incorrectly. Workaround: None.
N/A	`Error: 584 Message: Server public key verification failed` when running the diagtool.exe tool. Workaround: Either: Run the diagtool.exe tool from another host, or, Edit the registry on the machine where the diagtool.exe tool is being run: Remove the HKCU\Software\Sybase\Messaging Client registry key. Remove the HKCU\Software\Sybase\MessagingClientLib registry key. Note: Use caution when editing the registry. Ensure that the key entries removed do not contain any currently used SAP Mobile Platform applications (sub entries).
CR-709892	SAP Mobile Server records deployment errors in the domain log rather than in the SAP Mobile Server logs. Workaround: None. Look for deployment errors in the domain log.
CR-708431	Data on the EIS, cache, and device is not in sync. 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 SAP Mobile 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).
CR-703515	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 user name, DefaultSearchBase, AuthenticationSearchBase, RoleSearchBase, AuthenticationFilter, and RoleFilter. Workaround: None.
CR-701975	When deploying a package from Unwired WorkSpace or SAP Control Center using Update mode, the package's "onDemand" coherence window is not updated on SAP Mobile Server. Workaround: After deployment, adjust the "onDemand" coherence window from SAP Control Center.
CR-699590	Large messages are processed incorrectly on 32-bit runtime installations. A 32-bit SAP Mobile 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 SAP Mobile Server cache. Workaround: Install SAP Mobile Platform runtime components on 64-bit hosts.
CR-699343	For native Object API applications, the upgrade process silently deletes composite orphans from the server cache. SAP Mobile 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. Workaround: Before upgrading, eliminate composite orphans from native Object API applications: Look for existing MBOs that generate composite orphans. Examine each MBO in Unwired WorkSpace, looking for any instance in which the application loads child entities before the related parent entity. For any MBOs you find that generate composite orphans, change the data model in the MBO so that the application always loads parent entities before the related child entities. See the "Composite relationship behavior" row in the Relationship Guidelines and Restrictions topic, in the Sybase Unwired WorkSpace - Mobile Business Object Development guide. Test any changes you make to ensure that the application still behaves as expected. After you are satisfied that you have eliminated composite orphans from your MBOs, proceed with the upgrade. 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. To be sure that composite orphans do not cause problems in your migrated applications: After migration, if you have mobile application projects that contain composite relationships and the child MBO load operation has no parameter dependencies on its parent, redeploy the package from Unwired WorkSpace using Update mode to generate the correct loadGroups for the deployed package. Child load operations that do not depend upon parameters from the parent do not always generate orphans. Consider the case where the user wants to load all sales orders and line items created in the New York office. New York may be a load parameter for both parent and child that is bound to a personalization key and results in no orphans even though the child does not get any load parameters from the parent.
CR-695671	The mlsrv_err.log reports error: `java.lang.OutOfMemoryError`. 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 SAP Mobile Server Performance Properties in System Administration.
CRs 693116 and 692218	Devices on 3G/4G network cannot connect to SAP Mobile Server. A connectivity issue may occur between the device and SAP Mobile 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. Note: For devices on Wi Fi networks, the connection between a device and SAP Mobile Server establishes without error. Workaround: Use a nonstandard HTTP port (any port other than 80 or 8080) or an HTTPS port, that is, 443 for SAP Mobile Server client communication from devices to the Relay Server or external load balancer, whichever one is used, in the DMZ.
CR-692374	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 SAP Mobile Platform Developer Guides to enable compression.
CR-691517	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.
CR-686043	In a disabled domain, 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.
CR-576726	The full range of valid values is not supported if an 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.`
NA	When stopping the Windows service for SAP Mobile Server, very infrequently the process stops responding. This problem is independent of the means used to stop the service. When this happens, the process tree for the service for the SAP Mobile Server service is no longer intact, so you cannot use the Task Manager End Process Tree option to stop the service. Workaround: Open Windows Task Manager on the system where you want to stop the SAP Mobile Server service. Activate the Process tab and click the Image Name column heading to sort the names in alpha order. For each of the following processes that are present in the list, right-click the process and select End Process. AdminWebservices.exe AMPService.exe Dbsrv16.exe Dbsrv11.exe Java.exe JmsBridge.exe LBManager.exe mlsrv16.exe MlsrvWrapper.exe OBMO.exe OBServiceManager.exe Rsoe.exe Sccservice.exe wmiprvse.exe Go to the Windows Services panel and verify that the SAP Mobile Server service is stopped.