Issue Details (XML | Word | Printable)

Key: CORE-5757
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Alexander Peshkov
Reporter: Hamish Moffatt
Votes: 0
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
Firebird Core

deadlock with events

Created: 22/Feb/18 03:18 AM   Updated: 25/Mar/18 07:40 AM
Component/s: Engine
Affects Version/s: 4.0 Initial, 3.0.0, 2.5.6, 3.0.1, 2.5.7, 3.0.2, 4.0 Alpha 1, 2.5.8, 3.0.3
Fix Version/s: 3.0.4, 4.0 Beta 1, 2.5.9

File Attachments: 1. Text File after-patch.txt (7 kB)
2. Text File after-patch2.txt (21 kB)
3. File event_loop.py (0.8 kB)
4. File event_loop.py (0.5 kB)
5. Text File gdb.txt (5 kB)
6. Text File PORT_connecting.patch (8 kB)

Environment: Linux

QA Status: Done with caveats
Test Details:
Stored as usual Python script, for usage only in separate POSIX environment.
Must NOT be launched together with other tests from fbt-repo!

See: fbt-repo/files/core_5757.py.txt


Sub-Tasks  All   Open   

 Description  « Hide
My Firebird server deadlocks often. I am using 2.5.8 on Linux in a mix of superserver, superclassic, 32-bit and 64-bit. All are affected.

When this happens I cannot make any new connections or run any queries on existing connections.

This looks just like CORE-4680 which was meant to be fixed in 2.5.5.

I created a Python program which connects to the server, registers an event listener then disconnects. It runs 5 threads at once. The server deadlocked after about 300 connects (64 connections on each thread). When I killed the Python program the server resumes. The test database is any empty database.

I have attached a back trace from the server while it's in this state.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no subversion log entries for this issue yet.