You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using FB 3.0.3.329 as an embedded server it crashes after a connection has been in use for 110 seconds in 50-60% of instances. Seems to be similar to an issue reported when using 2.5 & 3.0 simultaneously and running backups but occurs when just using 3.0 and a prepared command .
To reproduce the error:
Create a database with 1 table & 2 fields.
Create a connection to the database & then a FbCommand with 1 lookup parameter to select a record from the table & call .Prepare() on the FbCommand.
In a loop provide a value for the parameter & call the prepared FbCommand.
In 50-60% of runs firebird crashes after 110 - 115 seconds. Connection Pooling & lifetime settings appear to have no effect & once the error occurs the only way to establish a new connection to any database is to stop & restart the process. This does not happen with Firebird 2.5.8 or any other 2.5.x version we've used.
The text was updated successfully, but these errors were encountered:
Submitted by: Danie Brink (brinkdg)
When using FB 3.0.3.329 as an embedded server it crashes after a connection has been in use for 110 seconds in 50-60% of instances. Seems to be similar to an issue reported when using 2.5 & 3.0 simultaneously and running backups but occurs when just using 3.0 and a prepared command .
To reproduce the error:
Create a database with 1 table & 2 fields.
Create a connection to the database & then a FbCommand with 1 lookup parameter to select a record from the table & call .Prepare() on the FbCommand.
In a loop provide a value for the parameter & call the prepared FbCommand.
In 50-60% of runs firebird crashes after 110 - 115 seconds. Connection Pooling & lifetime settings appear to have no effect & once the error occurs the only way to establish a new connection to any database is to stop & restart the process. This does not happen with Firebird 2.5.8 or any other 2.5.x version we've used.
The text was updated successfully, but these errors were encountered: