SQL Anywhere 17 Ultralitej - how to detect error [-10279] in Java code

[markturner3]

Some test users of our Android app are repeatedly getting a MobiLink Server Error "[-10279] Connection was dropped due to lack of network activity" at the end of the MobiLink synchronisation process initiated on the mobile client. A partial example from the server log is:

I. 2023-11-28 17:04:48. <4842> Request from "UL 17.0.7254" for: remote ID: a1c887fa-8c28-11ee-8000-a1b2854653c3, user name: MobilinkSMPLProd, version: ul_default
I. 2023-11-28 17:04:48. <4842> The current synchronization is using a connection with connection ID 'SPID 69'
I. 2023-11-28 17:04:48. <4842> COMMIT Transaction: Begin synchronization
I. 2023-11-28 17:04:48. <4842> COMMIT Transaction: Upload
I. 2023-11-28 17:04:48. <4842> COMMIT Transaction: Prepare for download

I. 2023-11-28 17:05:03. <4842> Sending the download to the remote database
I. 2023-11-28 17:05:11. <4842> COMMIT Transaction: Download
I. 2023-11-28 17:05:11. <4842> COMMIT Transaction: End synchronization
E. 2023-11-28 17:09:48. <4842> [-10279] Connection was dropped due to lack of network activity
I. 2023-11-28 17:09:48. <4842> Synchronization complete

Is there a way to trap this error in the Java code of the Android app? I am using Android Studio and the UltraliteJ library. If not, can anyone suggest why this may be occurring? Unfortunately the test users I am referring to are "Google Play" testers and they refuse to engage in any dialogue to assist.

[chris_keating]

You should be able to capture an exception (ULjException) on the client side. But it wmay direct you back to the MobiLink server for details of the error ( Error Code -857).

The error appears to be a timeout - there is a 4 minute gap between the End Synchronization transaction and the error. Assuming that the network is stable, this might translate into some intermediary such as a firewall, proxy and so forth interrupting or blocking packet traffic.

Or is the UltraLite application dropping the connection (crash, forced shutdown) during a sync?

How large is the sync? .

[markturner3]

Many thanks for the comment, Chris. The sync is tiny, just a few small tables. I suspect you are right about timeout being the probable cause. This would have to be at the "Google Play" test environment where they are emulating our mobile client app. My test environment on both emulator and real Android phone works fine and I cannot replicate their error.