| Subject | Re: [firebird-support] A Bunch of ibserver processes on Linux |
|---|---|
| Author | Milan Babuskov |
| Post date | 2004-01-05T15:58:36Z |
Kris Balle Kristensen wrote:
Firebird version (with PHP clients) on Mandrake Linux for over a year
and have had no such problems.
Probably so of the components don't release the connection. It is also
possible that you have "inteligent" users who, when they don't get fast
response, click the button again and again increasing the load on the
server. If this is the case I recommend you Classic server.
http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_ss_vs_classic
There isn't a one-fits-all version and it doesn't depend on the
distribution you're using, but rather on the problem at hand. If you
have demands for both long-running queries and short transaction, then
go with Classic. If you only have short-transactions and rare
long-running queries (monthly reports, etc.) use SuperServer.
can't answer your final question, though, so I hope someone will jump in.
HTH
--
Milan Babuskov
http://fbexport.sourceforge.net
> Env:It's probably the problem in your code or JBoss or JBird. I use the same
> Linux Redhat server 7.3 + upgrades
> JBoss 3.0.8 + patches
> Firebird SS version 1.0.3.972
> JBird JDBC-driver 1.0.1
>
> I just got a mail from our 1 line support explaining that one of our customers counted no less than 165 ibserver processes on the Linux box, which made it impossible to login to the system. We tried to kill all these processes (alll but 6 had the same parent process) and tried login again to no avail. Finally we rebooted the Linux box and everything went back to normal.
>
> Anybody seen this kind of behaviour on Linux before? If so how to avoid it?
Firebird version (with PHP clients) on Mandrake Linux for over a year
and have had no such problems.
Probably so of the components don't release the connection. It is also
possible that you have "inteligent" users who, when they don't get fast
response, click the button again and again increasing the load on the
server. If this is the case I recommend you Classic server.
> I seems like the CS version is the only version being upgraded and refactored from the firebird team. Is that right?AFAIK, no.
> What is the difference between the CS & SS version of Firebird? and what version would you recommend for Redhat?You can read about the differences here:
http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_ss_vs_classic
There isn't a one-fits-all version and it doesn't depend on the
distribution you're using, but rather on the problem at hand. If you
have demands for both long-running queries and short transaction, then
go with Classic. If you only have short-transactions and rare
long-running queries (monthly reports, etc.) use SuperServer.
> We have another problem regarding the connection management. I'm not sure about this one, but it looks like the driver is not cabable of returning not used connections back to the JBoss management pool. I read from your download page that a new version of the JDBC driver for CS 1.5 has arrived where this issue should be fixed. Will this new version only work with CS 1.5 or can I use with SS as well?It seems to me that it is the same problem as those 165 connections. I
can't answer your final question, though, so I hope someone will jump in.
HTH
--
Milan Babuskov
http://fbexport.sourceforge.net