|Subject||Re: Another "connection forcibly closed by the remote host" problem|
> > --- In email@example.com, "Adam" <s3057043@> wrote:OK - If it sounds to good to be true... I ran this test and got the
> Perhaps you could write a SQL Script that looks like this (from the
> problem workstation):
> select 1 from RDB$DATABASE;
> Then you can make a batch file that looks something like:
> "C:\Program Files\Firebird\Firebird_1_5\bin\isql.exe"
> servername:alias -user sysdba -password masterke -i
> Run the batch file to confirm it works.
> Now add it to the windows scheduled tasks to run every 20 minutes >
> and see if you can duplicate your problem.
same result. I'm now trying to pin down when the connection actually
dies. I checked the first time at 80 minutes and it was gone. I'm
stepping back to 60, then I'll back off 15 minutes until I find a live
connection, then bump up in 5 minute increments until it breaks again.
I also want to make sure that the disconnect point is consistent. It
seems to me that if the connection is consistently broken at 60
minutes (or some other point) that it almost certainly points to a
configuration setting in either FB, Win2003, or VMWare. I tend to
think that it is not VMWare after the successful test on the localhost.