XNET classic server client connection process timeout failure blocks subsequent connect attempts [CORE2808]

[firebird-automations]

Submitted by: Brenden Walker (braindead)

When the client times out waiting for xnet_response_event, the client exits clean. The server however continues on and sets the xnet_response_event.

This event sits out there for the next client who happily 'grabs' onto it and thinks a connection has been established. The response.map_num is XNET_INVALID_MAP_NUM and the client errors out. Once a timeout happens no further XNET connections can be made until the server is restarted as each client will grab the previous clients event.

I've seen similar symptoms on 2.1.3, however the cause in the cases I've been able to adequately review has not been due to exceeding xnet_connect_timeout. When I get more information on that I'll post a new issue.

Workaround for this particular problem is to increase the timeout via new config file parameter created in CORE2769

[firebird-automations]

Modified by: @pcisar

reporter: Pavel Cisar [ pcisar ] => Brenden Walker [ braindead ]

security: Managers [ 10013 ] =>

[firebird-automations]

Modified by: @dyemanov

assignee: Vlad Khorsun [ hvlad ]

summary: XNET classic server client connection process timeout failure blocks subsequent connect attempts. => XNET classic server client connection process timeout failure blocks subsequent connect attempts