Connection could hung after no activity for 60 seconds ------------------------------------------------------
Key: CORE-5911 URL: http://tracker.firebirdsql.org/browse/CORE-5911 Project: Firebird Core Issue Type: Bug Components: Engine Affects Versions: 3.0.3, 2.5.8, 4.0 Alpha 1 Environment: INET connections only Reporter: Vlad Khorsun Imagine application that run some query then sleep for 60 seconds then again run query, sleep for 60 sec and so on. If there are no other connections, or if this is ClassicServer - there could happen a race condition when last (only) worker thread in network listener exits due to idle timeout (60 sec) and new request is arrived at the same time and left not processed in queue. In the case of SS\SC any new request from the other connection will "awake" network server and that request will be processed, but in the case of CS this is impossible and connection will hung. The bug is at the thread pool of network listener and can't happen for XNET and WNET protocols which not uses thread pool. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel