Subject Re: Another "connection forcibly closed by the remote host" problem
Author Scott Moon
--- In, "Adam" <s3057043@...> wrote:
> --- In, "Scott Moon" <smoon63@>
> wrote:
> >
> > Adam,
> > Thanks for the reply. First things first, the programs we are
> > have been in use (with a number of upgrades and the usual
> > maintenance) for several years, and the problems we are seeing
> > arose only after we upgraded to FB 1.5.3 from 1.0.3 and moved
> an
> > outdated Win2000 server to a much upgraded Win2003 server. We do
> plan
> > in the (hopefully near) future to move away from the BDE because
> > its numerous problems.
> >
> > Secondly, the problem is only occurring to individual users - the
> > Firebird service is running just fine. The applications also run
> > expected, unless the user leaves the app open and connected for
> > hour. I also had this happen to me today when I had Database
> > Workbench connected with an active SQL Query window open. When I
> > closed DBW I got the "connection was forcibly closed" error,
> is
> > exactly what is happening to the clients. If you reopen the app,
> > connects and operates just fine.
> >
> > Thanks,
> > Scott
> But have you checked the firebird.log?
> You will not notice a restarted service unless you are connected at
> the time it restarts. It only takes a second to restart.
> Adam

Yes - the last entry is from last Thursday when we started the server
up after our upgrade:

[servername] (Client) Thu May 18 18:06:23 2006
Guardian starting: C:\Program Files\Firebird\Firebird_1_5

That brings up another point - that's all that is in the log. Is
there a setting I'm missing that tells Firebird what and how much to
enter in the log? Be gentle - I've only been working with FB for a
few months. Most of my time has been spent with Oracle and SQLServer,
that will write volumes to the log.