Re: Dropped Sessions Pervasive v7
- From: "Bill Bach" <billbach@xxxxxxxxxxxxxxxxxxxx>
- Date: 30 Jun 2005 13:48:40 EDT
Pervasive is a slave to the TCP stack -- if the TCP connection is lost,
ther's not much that they can do about it (kind of like most
cellphones). There are numerous settings that yuou can adjust on TCP
as Windows registry hacks, but this can have an adverse effect on other
processes, and is not recommended. See an advanced text on Windows
registry hacks for more details.
As you can guess, Pervasive addressed this with PSQL2000i SP3 by adding
the ability to automatically reconnect lost sessions, but you indicated
that upgrading to a newer version is not an option for you. I would go
back to your 3rd-party developer and find out why they are making you
live with technology from the last century. ;-)
Goldstar Software Inc.
Building on Btrieve(R) for the Future(SM)
Bill Bach
BillBach@xxxxxxxxxxxxxxxxxxxx
http://www.goldstarsoftware.com
*** Chicago: Pervasive.SQL Service & Support - July 19-22 ***
*** Chicago: Pervasive DataExchange Class - July 27-29 ***
JBreits wrote:
> We are using Pervasive v7 with a 3rd party software. We can't upgrade
> Pervasive as the 3rd party software doesn't support it. We are using
> TCP/IP protocol to connect to a remote database. Approx 100 clients
> are using this software (not necessarily all at once).
>
> The problem that we are having is that the client sessions appear to
> be being dropped. Looking in to the PVSW.LOG file on a client machine
> shows lots of status 3111, 3112, and 10054 messages.
>
> I have looked these up and it appears that they are related to
> connections to the database server being dropped. I have talked to
> our IT dept and they claim that the network is just fine (of course).
> I even had them install a sniffer on the client and on the server to
> monitor transmissions. And for the 3 weeks that they monitored,
> everything went smoothly (of course)!!! So I got no help from them.
>
> It does seem that the problems coincide with periods of high network
> usage, mostly when our IT dept is pushing out updates to computers.
> They generally do these updates overnight and that's when the problems
> usually occurr. We have batch processes that run overnight and it is
> a real pain when they don't work.
>
> Lately, these "disconnects" have been occurring pretty much nightly.
> This coincides with the fact that IT is pushing out updates to McAffee
> v8 and Win XP SP2. Factor in the 5000+ computers that they are
> updating, and that makes for some heavy network traffic that could go
> on for weeks.
>
> I guess my main question is if there is a way to set Pervasive's
> Timeout value so it waits longer before deciding the connection was
> dropped? Or is there a way to set Pervasive to use retries?
>
> Checking the Pervasive setup on my local machine, I noticed TCP/IP
> Timeout value under Communications Requester. Could that be anything
> useful? It is currently set to 15.
>
>
> Server is Win2003 Server. Dual Intel Xeon processors. 6GB RAM.
> Clients are XP, P4's 256-512MB RAM.
>
> Thanks,
> JBreits
.
- Follow-Ups:
- Re: Dropped Sessions Pervasive v7
- From: Bill Bach
- Re: Dropped Sessions Pervasive v7
- References:
- Dropped Sessions Pervasive v7
- From: JBreits
- Dropped Sessions Pervasive v7
- Prev by Date: Re: NTDBSMGR Handles are going crazy
- Next by Date: Re: SQLDM - Critical error occured. Exception while initializing
- Previous by thread: Dropped Sessions Pervasive v7
- Next by thread: Re: Dropped Sessions Pervasive v7
- Index(es):
Relevant Pages
|
