SQL Anywhere ultralite - Re: Synch freezing in .Net

Author

Re: Synch freezing in .Net

Jonathan Chapman

2006-03-23, 1:24 pm

We actually waited and it did stop after 2 hours with a communication error.
Is there a setting that would make it wait that long? The normal wait time
that I have experienced, in other situations, is 2 minutes.

Thanks,
Jonathan

"Jonathan Chapman" < jonathan_chapman@ape
xsi.com> wrote in message
news:4421b9a2$1@foru
ms-2-dub...
> Hi,
> I'm using the 9.0.2 Build 3267 Ultralite .Net component on a Pocket PC
> 2003 device with a 802.11b wireless card.
>
> If I go out of coverage and then go in and out of coverage along the
fringe
> my synchronization will eventually hang. My call is
> iAnywhere.Data.Ultralite.ULConnection conn;
>
> ....
>
> pub = conn.Schema. GetPublicationSchema
("Security");
>
> oldMask = conn.SyncParms.PublicationMask;
>
> conn.SyncParms.PublicationMask = pub.Mask;
>
> conn.SyncParms.UserName = loginID;
>
> conn.SyncParms.Password = password;
>
> if (newPassword != null && newPassword != "")
>
> {
>
> conn.SyncParms.NewPassword = newPassword;
>
> }
>
> conn.Synchronize();
>
> Sometimes I never return from the conn.Synchronize. The wait cursor I
have
> just continues to spin.
>
> Any ideas?
>
> Note: When I do the synch with the listener I can also get this to happen.
> In addition it will happen in the fields with a WWAN connection.
>
> Thanks,
>
> Jonathan
>
>
>

Greg Fenton

2006-03-23, 1:25 pm

Jonathan Chapman wrote:
> We actually waited and it did stop after 2 hours with a communication error.
> Is there a setting that would make it wait that long? The normal wait time
> that I have experienced, in other situations, is 2 minutes.
>

Have you read:

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

The important thing to walk away from the above document is that
changing the default timeout behaviour of the OS (which is 2 hours) is
the better solution.

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

Jonathan Chapman

2006-03-24, 11:25 am

I have made this change and it seems to work in some circumstances. We are
still verifying all situations. The one question I have is how to do the
same thing for TCPIP6. TCPIP6 already has the registry keys. When I change
the timeout to 30 seconds and reboots it keeps on getting set back to
7200000. Do you know what may be setting this back?

Thanks,
Jonathan
"Greg Fenton" <greg. fenton_NOSPAM_@ianyw
here.com> wrote in message
news:4422b5bc$1@foru
ms-2-dub...
> Jonathan Chapman wrote:
error.[color=darkred]
time[color=darkred]
>
> Have you read:
>
> http://www.ianywhere.com/developer/...link_tcpip.html
>
> The important thing to walk away from the above document is that
> changing the default timeout behaviour of the OS (which is 2 hours) is
> the better solution.
>
> Hope this helps,
> 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