At 10:28 PM 28/09/2010, Niall Naughton wrote: >Just recently we have been experiencing a lot of our firebird installations >generating errors of type 'Error reading data from the connection.'. Our >Firebird installations are of the 'Classic' type and have used version 1.5.2 >for the past few years.
A lot of years, actually. The current (and last-ever) sub-release of the 1.5 series is 1.5.6. There are very strong reasons to update your version. Download the v.1.5.6 release notes and read the Bug fixes (which includes closure of security vulnerabilities) for sub-releases 1.5.3 through 1.5.6. >Our .Net based software connects with the FirebirdSql.Data.Firebird dll >(version 1.0.1241.28320). To date our installations have caused very few >incidents of the above error. In recent months the frequency of these error >has grown considerably and is now a serious concern for us. > >The errors are sourced to mainly the >FirebirdSql.Data.Firebird.FbResultset.Fetch() call. While the FirebirdFaq site >states that this error is: >a) someone rebooted or restarted the server >b) Firebird server crashed >this contradicts the fact that other PC's that are also connected to the same >Server and not generating these errors. No, it doesn't. Each client instance has its own individual instance of the Classic server. >Some PC's seem to experience these problems more frequently than others >connected to same server. >Furthermore, while the Fetch() is the main source of these errors, this error >is also (to a lesser extent) sourced by the calls >FirebirdSql.Data.Firebird.FbConnection.Close() >FirebirdSql.Data.Firebird.FbStatement.DropStatement(). > >Is there a reason why we should expect the Fetch( ) call to be the main source >of these errors? Is this error an issue with Firebird itself? Very likely you will find more than one relevant issue has been fixed in the subsequent sub-releases. However, don't overlook the possibility that you have a bad UDF that is called by some clients and not others. Once the bad UDF has crashed the server, all subsequent requests (fetches, closes, dropStatements, etc.) will return the network error. >We are under a lot of pressure to resolve this issue, and we'd appreciate any >help that anyone can give us. I'll leave others to advise on any known issues with that old provider version - it's not my part of ship. However, I urge you to make deploying v.1.5.6 a high priority. Also make sure that the databases are not being subjected to filesystem utilities like backups, SystemRestore, et al., when there are connections to them. Get your databases excluded from these operations and use gbak regularly. Helen ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
