New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XNET protocol does not work correctly in SuperClassic [CORE1902] #901
Comments
Commented by: @hvlad This is because of following code in server_init() :
#ifdef SUPERSERVER Remove #ifdef, please, and tell if error gone |
Commented by: @alexpotapchenko Yes, if global_slots_per_map = XPS_MAX_NUM_CLI then XNET protocol in SC works correctly. |
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
Commented by: @alexpotapchenko If I am not mistaken in server_init() the following code is necessary: |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5 Alpha 1 [ 10224 ] |
Commented by: Philip Williams (unordained) Would you expect to see this issue in Firebird 2.1.1 SuperServer on Win x32? I had that happen to me today, probably while a cron job was talking to the database (via an isql script, running on the same machine as the server process, connecting locally -- but I don't have any stderr logs from that isql session.) From firebird.log: PTC-DEV2-XP (Server) Tue Oct 07 09:13:02 2008 PTC-DEV2-XP (Server) Tue Oct 07 09:13:02 2008 |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Cannot be tested |
Submitted by: @alexpotapchenko
XNET protocol does not work correctly in SuperClassic if there are multiple connections.
In log file:
XNET error: get_free_slot() failed.
It occurs because in function xnet::get_free_slot it is not possible to create map file because the map file with such name is already created.
The reason of it that code in xnet::connect_server (ULONG timestamp = (ULONG) time(NULL);) does not generate unique value.
Commits: 7d28033
The text was updated successfully, but these errors were encountered: