Release Candidate 1
|
R E G R E S S I O N S F I X E D |
ISSUE |
Tracker #
Fixed by |
EXECUTE STATEMENT could cause a core dump |
CORE-921 |
A bug was causing a core dump in stored procedures using EXECUTE STATEMENT. |
A. Peshkoff |
|
L E G A C Y B U G S F I X E D |
ISSUE |
Tracker #
Fixed by |
Transaction ID Overflow |
CORE-1042 |
Transaction numbers could overflow the 32-bit signed integer and corrupt the database. |
V. Horsun |
|
Possible stack corruption in the deferred work handler. |
CORE-1051 |
Fix to problem backported from Firebird 2.0. |
V. Horsun |
|
Source of 10048 Network Errors Found and Fixed |
CORE-966 |
Socket binding for events exhibited a bug where 10048 network errors were being reported in the log when clients attempted to bind to events. |
P. Beach,
D. Yemanov |
|
Server freeze caused by unavailable events port |
CORE-157,CORE-363 |
In previous versions of Superserver, if the server could not establish a socket for events, e.g. a firewall prevented the event port from being opened at the server side, the server would hang when a client attempted to register for an event. Connected clients would stop responding and new connections would be blocked.
Now, under these conditions, the client will hang until the socket call times out (by default, 10 seconds) and then the server will respond to the isc_que_events() call by throwing the exception isc_net_event_connect_err, "Failed to establish a secondary connection for event processing" and will continue to serve user requests normally.
|
P. Beach,
A. Peshkoff |
|
AV's with Read-only Read Committed Transactions on Classic |
CORE-911 |
Access violations (segfaults) could occur in the Classic server when clients woke up after leaving read committed read-only transaction active but idle for long periods. |
V. Horsun |
|
Isql didn't detect when its buffer was full |
Unregistered bug |
When the buffer overflowed in isql, the error was not detected. |
P. Beach,
D. Sibiryakov |
|
Isql had some problems handling quoted strings. |
Unregistered bug |
Fix back-ported from Firebird 2.0. |
P. Beach,
D. Sibiryakov |
|
Gstat unhelpful reporting Win32 error messages |
Unregistered bug |
On Windows, GSTAT would print "unknown Windows NT error" instead of a proper Win32 error message. |
C. Valderrama |
|
BUGCHECK(183) Error |
CORE-973 |
A condition was causing BUGCHECK(183) when attempting to back out a record version after a crash. |
A. Harrison |
|
M I N O R E N H A N C E M E N T S |
ISSUE |
Tracker #
Fixed by |
|
N O N E |
N/A |