|
Hi, I've got the above error from and Android application, I do have the INTERNET permission set. I have two test apps which just try to register and sync. the connection code is taken from the SUP101 example, and just adds the FarmID to work via relay server. One for the SUP101, which works, thus verifying the network settings are OK? One for my project which gives this error ( different user, AppID and XXXDB class, all else the same ). 02-28 16:59:11.280: W/System.err(2238): com.sybase.persistence.SynchronizeException: com.ianywhere.ultralitejni12.implementation.JniException: UltraLiteJ Error[-1305]: MobiLink communication error -- code: 63, parameter: , system code: 110Details: 02-28 16:59:11.280: W/System.err(2238): StreamErrorCode = 63 02-28 16:59:11.280: W/System.err(2238): StreamErrorMessage = null 02-28 16:59:11.280: W/System.err(2238): at com.sybase.sup.client.persistence.RbsDatabaseDelegate.internalSynchronize(RbsDatabaseDelegate.java:807) 02-28 16:59:11.280: W/System.err(2238): at com.sybase.sup.client.persistence.RbsDatabaseDelegate.synchronizeWithCallback(RbsDatabaseDelegate.java:419) 02-28 16:59:11.290: W/System.err(2238): at com.sybase.sup.client.persistence.RbsDatabaseDelegate.synchronize(RbsDatabaseDelegate.java:1168) 02-28 16:59:11.290: W/System.err(2238): at com.sybase.sup.client.persistence.RbsDatabaseDelegate.synchronize(RbsDatabaseDelegate.java:1159) 02-28 16:59:11.290: W/System.err(2238): at UKPNCat.SUPModel.UKPNCatalogueDB.synchronize(UKPNCatalogueDB.java:198) 02-28 16:59:11.290: W/System.err(2238): at com.example.suptestukpn.MainActivity$1.run(MainActivity.java:78) 02-28 16:59:11.290: W/System.err(2238): Caused by: com.ianywhere.ultralitejni12.implementation.JniException: UltraLiteJ Error[-1305]: MobiLink communication error -- code: 63, parameter: , system code: 110 02-28 16:59:11.290: W/System.err(2238): at com.ianywhere.ultralitejni12.implementation.JniConnection.ulcSynchronize(Native Method) 02-28 16:59:11.290: W/System.err(2238): at com.ianywhere.ultralitejni12.implementation.JniConnection.synchronize(Unknown Source) 02-28 16:59:11.290: W/System.err(2238): at com.sybase.sup.client.persistence.RbsDatabaseDelegate.internalSynchronize(RbsDatabaseDelegate.java:707) 02-28 16:59:11.290: W/System.err(2238): ... 5 more Earlier I get a 6600 error, which I've not yet been able to understand. 02-28 16:58:15.670: I/MocaLog(2238): 28T165815, T1, Caught Exception in AwaitingServerRequest. Error: Error: 6600 Message: 'Request Cancelled' 02-28 16:58:15.680: I/MocaLog(2238): 28T165815, T1, processTillStoppedGuts caught exception: Error: 6600 Message: 'Request Cancelled' … 02-28 16:58:15.670: I/MocaLog(2238): 28T165815, T1, Caught Exception in AwaitingServerRequest. Error: Error: 6600 Message: 'Request Cancelled' … 02-28 16:58:15.690: I/MocaLog(2238): 28T165815, T1, Previous 6600 error has been ignored due to stopping Any hints and tips gratefully received. |
|
Stream error 63 is "unable to connect socket". http://dcx.sybase.com/index.html#1201/en/saerrors/mlcommerr63.html If this synchronization is going through the Relay Server, you have likely specified and incorrect host or port number for the Relay Server, or the Web Server isn't running that is hosting the Relay Server. Thanks, but it's the same setup as the SUP101 test app, which doesn't get the error ( pretty much the same app, same device, same servers, same networks ). It seems to have "gone away" after resetting the device via SUP SCC... I saw this mentioned by someone else ( somewhere... ), so it looks like this error can occasionally by misleading? Maybe the connection was being refused due to the earlier 6600 error ( which I think has also gone away... ).
(01 Mar '13, 08:21)
Barnie
Replies hidden
I'm afraid I don't know what resetting the device via SUP SCC means, but from a UL/ML perspective, I tell you with a lot certainty that if stream error 63 is returned, it's because UL attempted to open a socket on machine X, port Y, but the socket open failed.
(01 Mar '13, 11:23)
Reg Domaratzki
1
I too am not an expert on the SUP layers that use UltraLite. But I can say that the system code 110 is ETIMEDOUT from the Linux errno.h.
(01 Mar '13, 14:03)
Andy Quick
|
