|
Home > Archive > SQL Anywhere Mobile > November 2005 > Upload problem
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]
|
|
|
| Hi all,
mobilink 9.0.2.3198
UL 9.01.1751
here is the scenario:
1)i upladed rows from the ppc to the mobilink but the
mobilink was shutdown ,
2) the next time i up uploaded the mobilink was up but the
rows that was previosley sended apperentley marked as "sent"
and didn't send again.
3) but they didn't send before because the mobilink was down
how i solve this problem??
have GREAT day
Omri Ziv
| |
| Greg Fenton 2005-11-22, 11:24 am |
| Omri wrote:
> here is the scenario:
> 1)i upladed rows from the ppc to the mobilink but the
> mobilink was shutdown ,
> 2) the next time i up uploaded the mobilink was up but the
> rows that was previosley sended apperentley marked as "sent"
> and didn't send again.
We'd need to see a repro of this problem. UltraLite should not mark the
"upload" as complete until it begins receiving a download. If ML was
not running, then the download could never have been received so the
upload would fail and be tried again on the next synchronization.
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
| |
|
| > Omri wrote:
> We'd need to see a repro of this problem. UltraLite
> should not mark the "upload" as complete until it begins
> receiving a download. If ML was not running, then the
> download could never have been received so the upload
> would fail and be tried again on the next synchronization.
>
ML 9.0.2.3198
UL 9.0.1.1751
1) what do you mean by "repro" ?
2) i know it's usualy like this but i have like 80 terminals
(ppc) and all of them had this problem, my ML was DOWN and
they try to upload (GPRS) but the got a "communication
error" ( they got it after 7-8 min do you have a parmeter to
limit the synchronyze command in the ppc? and not the
keep_alive in the registrey).
but when the communication was back the rows didn't sent
again?
weird very weird,
Have a GREAT day,
Omri Ziv,
| |
| Greg Fenton 2005-11-23, 8:24 pm |
| Omri wrote:
> ML 9.0.2.3198
> UL 9.0.1.1751
> 1) what do you mean by "repro" ?
I mean you need to create a scenario whereby anyone can follow *your*
steps one by one and reproduce (repro) the problem. Typically this will
involve you submitting a database and possibly a simplified UL
application, along with the steps to show exactly the problem you are
seeing.
> 2) i know it's usualy like this but i have like 80 terminals
> (ppc) and all of them had this problem, my ML was DOWN and
> they try to upload (GPRS) but the got a "communication
> error" ( they got it after 7-8 min do you have a parmeter to
> limit the synchronyze command in the ppc? and not the
> keep_alive in the registrey).
> but when the communication was back the rows didn't sent
> again?
>
Well, this means that there is a fundamental problem with either your UL
configuration or with UL itself. I would find it hard to accept that a
bug of this nature exists within UL (though I have been proven wrong in
the past).
Is there the possibility that your application is doing something after
the failed synchronization such as deleting rows?
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
| |
|
| > Omri wrote:
>
>
> Is there the possibility that your application is doing
> something after the failed synchronization such as
> deleting rows?
>
i hope that you don't wrong or else we have a huge problem
i'll check again all the system again.
but you didn't refer to the limit the synchronization(even
thoguh it's in brackets it is more immportant) i need a
command or parameter that can limit the time of
synchronization from client side (ppc).
Have a GREAT day
Omri Ziv
| |
| Greg Fenton 2005-11-25, 8:24 pm |
| Omri wrote:
>
> but you didn't refer to the limit the synchronization(even
> thoguh it's in brackets it is more immportant) i need a
> command or parameter that can limit the time of
> synchronization from client side (ppc).
The 7-8 minute timeout problem is a problem with the Operating System,
not with UltraLite. The registry setting solution is put forward
because that is how to configure the OS.
UltraLite simply tells the OS to make a TCP/IP connection and to
retrieve data from that socket. It is the OS that goes away and does
not return until the timeout hits.
If you search this newsgroup (use Google Groups) for "keep_alive", you
will find many threads similar to this one.
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
| |
|
| ML 9.0.2.3198
UL 9.0.1.1571
what about this solution :
if i send ping only and the answer is not communication
error the i'll upload all the data.
the ping can be more faster them the upload isn't it?
i'll use try catch.
have a GREAT day
Omri Ziv
| |
| Greg Fenton 2005-11-27, 8:24 pm |
| Omri wrote:
> if i send ping only and the answer is not communication
> error the i'll upload all the data.
Do you mean a network ping (ICMP packets) or a MobiLink ping?
In the case of a ML ping, you will have the same issue as the UL client
will be trying to make a normal connection to ML. I cannot be sure
about the network ping case.
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
|
|
|
|
|