Subject | Re: [firebird-support] Re: Internal software consistency check (cannot start thread) |
---|---|
Author | Helen Borrie |
Post date | 2005-02-07T05:59:08Z |
At 03:19 AM 7/02/2005 +0000, you wrote:
since it doesn't (can't) spawn process threads. Could it be that your
application code is trying to thread connections using the libfbembed.so
client? In that case, don't let your application use libfbembed.so - its'
not threadsafe - use libfbclient.so instead.
If you can't predict the max. number of instances likely to be needed, or
are at risk of being resource-starved, you're probably going to do better
using Superserver.
Classic attachments are handled by the daemon xinetd. If you have plenty
of server resources, you can raise the instances parameter in xinetd.conf
to raise the bar. If you're fairly short of server resources, the default
might even be too high. For example on my N/b I have RH 8, which defaults
the instances to 60. I know that, for a 1.3 GHz machine with 512Mb of RAM
this would blow out resources.
Can't quite figure an obvious connection between a thread error and this
particular thing, though. Could be something else, e.g. you didn't say
which Linux you were using. It could be some kind of error caused by using
a Linux that has implemented the New Posix Thread Library (NPTL). Firebird
1.0.3 doesn't support it - you have to turn it off. Ask again if you don't
know how.
./hb
>--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...> wrote:You were reporting a thread error, which seems out of place for Classic,
> > At 11:57 AM 5/02/2005 -0600, you wrote:
> > >I'm running Firebird 1.0.3 (Linux).
> >
> > Classic or Superserver?
>
>Superserver (sorry about leaving that out of the info -- didn't think
>about it).
since it doesn't (can't) spawn process threads. Could it be that your
application code is trying to thread connections using the libfbembed.so
client? In that case, don't let your application use libfbembed.so - its'
not threadsafe - use libfbclient.so instead.
If you can't predict the max. number of instances likely to be needed, or
are at risk of being resource-starved, you're probably going to do better
using Superserver.
Classic attachments are handled by the daemon xinetd. If you have plenty
of server resources, you can raise the instances parameter in xinetd.conf
to raise the bar. If you're fairly short of server resources, the default
might even be too high. For example on my N/b I have RH 8, which defaults
the instances to 60. I know that, for a 1.3 GHz machine with 512Mb of RAM
this would blow out resources.
Can't quite figure an obvious connection between a thread error and this
particular thing, though. Could be something else, e.g. you didn't say
which Linux you were using. It could be some kind of error caused by using
a Linux that has implemented the New Posix Thread Library (NPTL). Firebird
1.0.3 doesn't support it - you have to turn it off. Ask again if you don't
know how.
./hb