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 (IPC) communication protocol does not work across sessions [CORE1133] #1555
Comments
Commented by: Diane Downie (dianedownie) When fbserver and fbclient are rebuilt with the attached changes, the XNET protocol does work correctly across sessions on Windows 2003. |
Modified by: Diane Downie (dianedownie)Attachment: xnet.h [ 10260 ] |
Commented by: @dyemanov You can make XNET working across sessions without rebuilding the source code. This is documented in firebird.conf, parameter IpcName. Unfortunately, the overall issue is wider than just the XNET protocol, there are other sync objects that should also be global. We're going to address this in the v2.1 release. |
Modified by: @hvladassignee: Vlad Horsun [ hvlad ] |
Commented by: Diane Downie (dianedownie) I see that you can change the server settings from firebird.conf, but it was unclear to me that the fbclient also reads the settings from firebird.conf. Is that so or is some special configuration required? |
Commented by: @dyemanov fbclient also reads firebird.conf. |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.1 [ 10041 ] |
Modified by: @hvladFix Version: 2.0.1 [ 10090 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Commented by: @pcisar Reopened to update ticket information. |
Modified by: @pcisarWorkflow: jira [ 11611 ] => Firebird [ 15452 ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: Diane Downie (dianedownie)
Relate to CORE1031
Attachments:
xnet.h
The XNET interprocess communication mechanism returns the error "database unavailable" when you attempt to connect to the firebird server from a process running in a different session. If you attempt to connect to the same database with a remote procotol such as tcp/ip, no error is generated.
Commits: b37d8d2 c0989bc
The text was updated successfully, but these errors were encountered: