Hi,
For the past few days, we are facing a problem of network connectivity between Android Phone and Mobilink. Our architecture is as follows :
Android Phone (Has Ultralite16 DB) -> Firewall -> Apache Relay16 (OS Cluster) -> Mobilink16 Server (1 & 2- both are in Active Active Mode) -> Sql Anywhere 16 DB
I had just renamed the version ID for security reasons.
For most of the users, we are getting the below error :
I. 2015-08-21 14:53:20. <57> Request from "UL 16.0.1691" for: remote ID: 255dab00-3f74-11e5-8000-92669d434cba, user name: 1213, version: xxxxxxxxxxxxx
I. 2015-08-21 14:53:21. <57> The current synchronization is using a connection with connection ID 'SPID 81169'
W. 2015-08-21 14:53:21. <57> [10017] The consolidated and remote databases have different timestamp precisions. Consolidated database timestamps are precise to 0 digit(s) in the fractional second while the remote database timestamps are precise to 6 digit(s)
W. 2015-08-21 14:53:21. <57> [10018] Resolve the timestamp precision mismatch by setting the SQL Anywhere DEFAULT_TIMESTAMP_INCREMENT option on the remote database to 1000000 and TRUNCATE_TIMESTAMP_VALUES to 'On'. UltraLite remotes must set the TIMESTAMP_INCREMENT option to 1000000
W. 2015-08-21 14:53:21. <57> [10020] The timestamp precision mismatch may affect upload conflict detection. Use the -zp option to cause the MobiLink server to use the lowest timestamp precision for conflict detection purposes
W. 2015-08-21 14:53:21. <57> [10015] Table 'RETAILER_ATTENDANCE' has at least one timestamp column. Due to a timestamp precision mismatch, uploaded timestamps can lose precision, defeating download filtering
I. 2015-08-21 14:53:21. <57> COMMIT Transaction: Begin synchronization
I. 2015-08-21 14:53:22. <57> COMMIT Transaction: Upload
I. 2015-08-21 14:53:22. <57> COMMIT Transaction: Prepare for download
I. 2015-08-21 14:53:22. <57> Sending the download to the remote database
I. 2015-08-21 14:53:22. <57> COMMIT Transaction: Download
I. 2015-08-21 14:53:22. <57> COMMIT Transaction: End synchronization
E. 2015-08-21 14:57:30. <57> [-10279] Connection was dropped due to lack of network activity
I. 2015-08-21 14:57:30. <57> Synchronization complete
I. 2015-08-21 15:54:20. <Main> COMMIT Transaction: End connection
I. 2015-08-21 15:54:20. <Main> Synchronization connection with connection ID 'SPID 81169' has been disconnected
This connection dropped due to lack of network activity is killing the sync sessions and users are not able to sync their data to Sybase. Please help in finding the root cause. I had enabled -V+ verbosity also but I didn't got any fruitful logs from that.
Device : Android KitKat OS
UDB : Ultralite 16.0.1691
Apache Relay : 16.0.1691
Mobilink : 16.0.1691
SqlAnywhere : 16.0.1691
Regards,
Bharani Dharan.K.