|
Home > Archive > SQL Anywhere Mobile > May 2005 > Mobile Link Error : Timed out while waiting for the next HTTP request in this synchronization
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 |
Mobile Link Error : Timed out while waiting for the next HTTP request in this synchronization
|
|
|
| Hi All:
We have the time out error for the MobileLink server when
downloading data from a large databases, One of the largest table has around
40000 rows , second large table has 4000 rows, The .udb file should be
5-7 M . The device we use is Pocket PC , Palm or tablet pc . We got this
error after 5 minutes for the first time sync. I believe that we use
redirector.
The following is the error message from MobileLink server log :
Error: Unable to write to the 'http' network connection. Timed out while
waiting for the next HTTP request in this synchronization.
Thanks for your help.
Jin
| |
|
| Hi Greg:
Thanks for your help. Ian , Will and I are working on this
problems. We are using HTTP redirector
to connect to ML server. Seems there are no error logs for both redirector
and IIS servers. We will try TCPIP later to see
if it is working. I will let you know the progress of this problem.
Thanks.
Qingbo Jin
"Greg Fenton" <greg. fenton_NOSPAM_@ianyw
here.com> wrote in message
news:42724bbe$1@foru
ms-2-dub...
> Hi Jin,
>
> I am moving this error message from your last post in the mBus newsgroup:
>
>
> --------------------------------------------------------------------------
--
end_download[color=d
arkred]
>
> -------------------------------------------------------------------------
>
>
> 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/
|
|
|
|
|