Unwired Server or RSOE Startup Problems

Problem: Problems, such as Unwired Server or RSOE failing to start, are encountered without any obvious error messages.

Explanation 1: This may occur if the Unwired Server host machine is running intrusion detection software, such as the McAfee Host Intrusion Prevention service. This may cause a connection from the CDB to the Unwired Server node to be flagged as an attack, and the CDB host to be added to the list of Blocked Hosts, preventing communication between Unwired Server and the CDB. The Unwired Server log reports connectivity problems with the CDB, and startup failure problems similar to:

YYYY-MM-DD HH:MM:SS.SSS ERROR MMS Thread-55 [com.sybase.djc.log.SystemExceptionLog] com.sybase.djc.DataStoreException was thrown by method com.sybase.djc.server.PartitionLock.updateLock(boolean)\ncom.sybase.djc.DataStoreException: Connection Failed: java.sql.SQLException: JZ006: Caught IOException: java.net.SocketException: Software caused connection abort: connect ...

Workaround 1: You may want to set up some exclusion rules to allow the required communication between the CDB and Unwired Server nodes. Use the following information to formulate the exclusion rules; rules may vary depending on the intrusion detection software used.

  • SQL Anywhere® to Unwired Server – SQL Anywhere sends UDP packets on port 2638 in response to discovery probes. The JDBC/ODBC client (on Unwired Server) sends a UDP broadcast on 2638 outbound to all servers on the local network(s) with the name of the database service to which the client is trying to connect. If a SQL Anywhere hosting the given database sees that UDP broadcast request, it responds with a UDP targeted directly back to the host that sent the broadcast.

    The installer also issues a 'dblocate' query, which receives UDP responses back from every SQL Anywhere on the local network. Unwired Server uses that to filter out < cluster-name > _clusterdb responses to form a list of reachable Sybase Unwired Platform clusters to populate the dropdown list for subsequent installs where the user is adding a new Unwired Server to an existing cluster. If Sybase Unwired Platform is installed in a cluster, the MobiLink™ services also open connections among each other to coordinate activities of the MobiLink farm. Those connections are on the MobiLink listener ports.

  • Sybase Unwired Platform to CDB – uses a JDBC connection through jConnect™ for JDBC™ driver. There are two kinds of protocols between Sybase Unwired Platform and CDB:
    • The MobiLink and CDB connection uses Command Sequence.
    • The jConnect for JDBC connection uses TDS.
  • RSOE to Relay Server – uses either an HTTP and HTTPS connection.
  • Unwired Server to Unwired Server – for administration communication uses:
    • Administration communication (MMS to MMS) uses IIOPS protocol by default.
    • Administration communication (MMS to Mobile Office service) uses IIOPS protocol by default.
  • Unwired Server to Advantage Database Server – uses an OLE DB connection through ADO driver.

Explanation 2: If .Net is present when Unwired Platform is installed, and the .Net installation is corrupt, the Unwired Platform installer does not detect the problem, leaves the corrupt .Net in place and Unwired Server does not start.

Workaround 2: Uninstall both Unwired Platform and .Net, then reinstall Unwired Platform, letting the Unwired Platform installer install .Net.

Parent topic: Troubleshooting Installation