SMP/SUP Side car/database tier hung while synchronizing data

[Former Member]

Hi,

The data tier server for the SMP/SUP mobile platform hungs up during synchronization. On going through errorlogs found the following errors,

I. 02/22 17:50:15.     TCPIP link started successfully
I. 02/22 17:50:15. Now accepting requests
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=java.lang.Thread
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:34. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:34. Disconnected TCPIP client's AppInfo: HOST=;PID=8356;EXE=com.sybase.djc.scheduler.Sche
I. 02/22 17:50:36. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:36. Connection terminated abnormally; client socket shut down
I. 02/22 17:50:36. Connection terminated abnormally; client socket shut down

no active blocking were observed when the sync is going on,unable to use mobilink monitor to see the processes.

I have been using the following URL to troubleshoot the issue https://wiki.scn.sap.com/wiki/display/SAPMOB/Understanding+the+'ml_database'+lock+warning+in+SUP

I have also setup tracing on default database which i assume is the cachedatabase but seems nothing is captured.

I am kind of new to SAP platforms and terminology and not sure if i am on right direction.

Thank you, Babji

[Former Member]

I have been troubleshooting from SQL Anywhere 16 scjview utility

[Former Member]

Hi Everyone,

On which server does the Mobilink server reside and how i do register DSN so that i can use it start ML monitor?

mluser -c “DSN=default-cdb;UID=dba;PWD=sql” -u mlmon -p mlmon the following syntax did return error stating that datasource not found i have changed the name to approriate cdb(default)

Thank you in advance, Babji

[Breck_Carter]

If you don't know where the MobiLink server resides (it can be anywhere), you probably need to learn about how your environment is set up.

The log you posted comes from a SQL Anywhere database server, possibly the consolidated database, but it could be a remote database.

The connections that are terminating all came from one process (PID=8356) and they all terminated at the same time.

The "com.sybase.djc.scheduler.Scheduler" may be part of the Sybase Enterprise Application Server, which may or may not have anything to do with MobiLink.

[Former Member]

Thanks a bunc Breck! i am sorry for my dumb questions,i am new to SQL Anywhere and SMP.Does the ml server usually reside on sql anywhere db server or the sup server? i am unable to use mlprof to capture long running sync's,can you help me understand in brief please.

[Breck_Carter]

Are you setting everything up yourself, or have you been assigned to work on an existing setup? ...those are two different situations; the first is solved by following the documentation, the second by examining all the computers involved to find where everything is running.

There is no "usually resides" rule for the MobiLink server. In high performance setups, the MobiLink server mssrv16.exe is usually placed on some other computer, different from the SQL Anywhere database, because the database is often a bottleneck for CPU and other resources. In simple setups, everything running at head office is often placed on the same computer.

You may not find many experts on SUP or SMP or EA Server on this forum; I am certainly not one 🙂