Home > Archive > SQL Anywhere Mobile > April 2005 > Re: Mobile Link Error : Timed out while waiting for the next HTTP









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Re: Mobile Link Error : Timed out while waiting for the next HTTP
Greg Fenton

2005-04-29, 11:26 am

Hi Jin,

I am moving this error message from your last post in the mBus newsgroup:

> ----------------------------------------------------------------------------
> --
> I. 04/28 23:06:53. <1.5> [cihipalmbmXeuW]: COMMIT Transaction: end_download
> I. 04/28 23:06:53. <1.5> [cihipalmbmXeuW]: Sending the download to the
> remote database.
> E. 04/28 23:10:18. <1.5> [cihipalmbmXeuW]: Error: Unable to write to the
> 'http' network connection. Timed out while waiting for the next HTTP
> request in this synchronization.
> I. 04/28 23:10:19. <1.5> [cihipalmbmXeuW]: Creating download cache file
> " C:\WINNT\TEMP\rd0000
0028"
> -------------------------------------------------------------------------



It does not appear to me that this is a MobiLink timeout issue (though
it *could* be). The timeout is happening less than 5 minutes into the
download transfer. If this was a timeout, I'd expect the timeout to be
exactly X minutes into the transfer (though TCP timeout is measured in
milliseconds, on most systems it is set to some multiple of 60000...on
Win32 the default is exactly 2 hours).

For details about MobiLink and TCP/IP timeout, see:

http://www.ianywhere.com/developer/...link_tcpip.html

Are you using the redirector or are you hitting the ML server directly
using HTTP ? If you are using the redirectory, you may have to look at
your webserver configuration and logs to see if there is some indication
of why the connection is being closed. Also, if you are using the
redirector, try synchronizing directly with the ML server just to reduce
the number of layers and see if the problem still exists.

Can you determine if there is possibly a break in the network layer
during this synchronization (i.e. is the device losing connectivity)?

Say "hi" to Sam and Ian for me (or are those two listening here as
well??) :-)

greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com