Subject | Re: Workaround for Core-1961? |
---|---|
Author | intermoves |
Post date | 2009-02-27T13:12:49Z |
Hello Dmitry,
thank you for your quick and qualified response.
connection have been closed. After looking at the source code at
http://fisheye1.atlassian.com/browse/firebird/firebird2/src/jrd/cch.cpp?r=1.129.2.16#l3772
and with our explanation it became clear to me that the observed
message probably has just
* the message code and
* the line of code where it is reported
in common with Core-1961.
explicitely configured the per_source parameter in the xinetd
configuration of the classic server (and increased in this way the
value opposed the default value of the centos box).
Greetings
Andreas
thank you for your quick and qualified response.
> This ticket mentions the bug in the database validation code, i.e. itNo, GFIX was not involved. The message was produced when client
> can be caused by the GFIX activity only. Is it really your case?
connection have been closed. After looking at the source code at
http://fisheye1.atlassian.com/browse/firebird/firebird2/src/jrd/cch.cpp?r=1.129.2.16#l3772
and with our explanation it became clear to me that the observed
message probably has just
* the message code and
* the line of code where it is reported
in common with Core-1961.
> BTW, do you use SuperServer or Classic? If the former, then a switch toYes, we already use the classic server and for more stability we
> Classic might help to prevent this error from happening.
explicitely configured the per_source parameter in the xinetd
configuration of the classic server (and increased in this way the
value opposed the default value of the centos box).
Greetings
Andreas