--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@i...>
wrote:

> Does the client get any message?

In most cases, nothing obvious.. All these are backends to Web
applications so it will throw strange errors depending on the data
dependencies..

>
> Very old. Fb 1.5 has had a lot of fixes in the past two years.
>

I know that..<G> But do you think that, given my platform I should
upgrade, such that it has a good chance of having a impact on this
problem. (These are production systems so it is not a trivial task)

>
> >Redhat 9 (with last updates available)
> > Kernel: kernel-2.4.20-30.9.i686.rpm
>
> A threading problem? For that build of Firebird you need to disable

NPTL

> on RedHat 9 by an environment setting (see release notes). Did someone
> perhaps apply an upgrade without checking whether it affected the
> environment variables?

No, nothing has changed over the last year.. I'm the only person that
has access to the machines.

... but obviously I also need to make a better point of reading the
release notes more throughly.... <embarassed grine>

>
> Database Usage:
> Databases: 14
> Max users (based on max connections allowed to DB Pools): 70
> Average Users (Based on Connections reported in

DatabaseWorkbench): 55

>
> =================
> You have users (at server level) and requests being processed for 14

databases.

>
> In SS, the number of users is always going to be less than the

number of

> process threads. I'd look at this limit of 70 connections. The

number of

> connection requests wouldn't need to exceed the average by much to

hit your

> connection limit.
>
> Run a ps -aux |grep fbserver to count the threads.

firebird 3676 0.1 3.4 343868 35196 ? 11:08 0:17 /opt/firebird....

..only returned this single record.. (in addition to the root ps process)

>
>
> >microps-185 (Client) Fri Jan 20 00:03:00 2006
> > INET/inet_error: receive in try_connect errno = 2
>
> Means a resource the client is connecting to isn't available. If

you have

> users connected to any databases then obviously the resource is
> *there*. Hence my first guess that, when you see network error 2, it's
> your connection pool limit kicking in.

I'll followup on this idea.. I reviewed the initial and max
connections to every app and made some adjustments..

I'll also monitor it more carefully..

Thank you for your suggestions..

John..