Firebird 4 IResultSet.fetchNext error

[eversun]

SVN version from last update (7807)

Problem appeared with FB4 (4.0.1) and fbclient same version, x86
After some short time of operation with massive select, update, transactions, etc, an error appeared:

Step 1
Error reading data from the connection.; GDS Code: 335544726; Code: -902 Message: IResultSet.fetchNext

Right next to that error:
Step 2
Error writing data to the connection.; GDS Code: 335544727; send_packet/send; GDS Code: 335544382;
Code: -902 Message: GET NEW TRANSACTION

Step 3
Connection is not opened yet

[marsupilami]

Hello eversun,

Step 1
Error reading data from the connection.; GDS Code: 335544726; Code: -902 Message: IResultSet.fetchNext

Right next to that error:
Step 2
Error writing data to the connection.; GDS Code: 335544727; send_packet/send; GDS Code: 335544382;
Code: -902 Message: GET NEW TRANSACTION

These two error messages usually mean that the connection was loast - it somehow got disconnected.

[eversun]

Possibly yes. But it never happened before with FB2.5 - I just had updated several instances to FB4 and got this problem. As the load is quite heavy, the problem appears after some hours of operation, maybe 6-12 hours.

And together with the Reconnect problem is causes total fault. Once this error appears, further operation shortly causes an AV and requires manual full SW restart

[marsupilami]

Hello Eversun,

Possibly yes. But it never happened before with FB2.5 - I just had updated several instances to FB4 and got this problem.

Did you check the log files of Firebird? "Error reading data from the connection." and "Error writing data to the connection." usually happen when Windows has to close the socket for some reason. This can happen due to a lot of problems like faulty network hardware and the like. If you want to simulate this problem: Just unplug your computer from the network and plug it in again. Windows will close all open sockets when the network gets disconnected. Some uses of mine had this problem too when using wireless networks. When they switched to cables things usually got better or vanished.
If you still think this is because of Zeos: The only thing that changes in Zeos when switching from Firebird 2.5 to Firebird 4: Zeos enables the use of the interface based API if it is available and it isn't forced to use the legacy API. On Firebird 2.5 the legacy API is the only one that is available.

And together with the Reconnect problem is causes total fault. Once this error appears, further operation shortly causes an AV and requires manual full SW restart

Did you check if the latest changes from the other thread help on the reconnect problem?

Best regards,

Jan