SAP Mobile Server Fails to Start Due to Incorrect JVM Settings

Problem: SAP Mobile Server fails to start because of incorrect JVM property settings.

The JVM maximum heap size is set too low and/or a JVM option is missing a space.

Solution: To add a space to a JVM option:
  1. Edit the SMP_HOME\Servers\UnwiredServer\Repository\Instance\com\sybase\sup\server\SUPServer\sup.properties file and search for DJC_JVM_USEROPTIONS.
  2. Add a space before the appropriate option, for example,-Dcom.sap.solutionmanager.url=<SolutionManager_URL>.
  3. Start the SAP Mobile Server by doing one of the following:
    • Clicking the Start SAP Mobile Platform Services desktop shortcut.
    • Run the start-unwired-server.bat from the command prompt.
Solution: To increase the maximum heap size:
  1. Edit the SMP_HOME\Servers\UnwiredServer\Repository\Instance\com\sybase\sup\server\SUPServer\sup.properties file and search for DJC_JVM_MAXHEAP.
  2. Increase this value. The default is 2048MB. Servers with 64-bit operating systems can be set much higher, depending on the available RAM.
    Note: For servers with 32-bit operating systems, the MAXHEAP value is limited to 768MB. Some machines will have a maximum that is less than that, for example, 512MB. If the MAXHEAP is set too high, errors are reported in the SMP_HOME\Servers\UnwiredServer\logs\mlsrv_err.log file.
  3. Start the SAP Mobile Server by doing one of the following:
    • Click the Start SAP Mobile Platform Services desktop shortcut.
    • Run start-unwired-server.bat from the command prompt
    Note: To make sure that SAP Mobile Server is reconfigured with the new heap size, make sure an empty sup.cff file exists in the SMP_HOME\Servers\UnwiredServer\bin\private folder. This file causes SAP Mobile Server to reconfigure when it starts up using the BAT file. If the file does not exist, create it. You can copy installdate.cff and rename it to sup.cff.
Parent topic: SAP Mobile Server