Database shutdown is reported as successfully completed before all active
connections are in fact interrupted
-------------------------------------------------------------------------------------------------------------
Key: CORE-4236
URL: http://tracker.firebirdsql.org/browse/CORE-4236
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 3.0 Alpha 1
Environment: SuperServer only
Reporter: Dmitry Yemanov
Database shutdown procedure was reworked in v3 and v2.5.3 to be more
synchronous than before and really wait until all running activities are
stopped, their changes are rolled back and all user connections are gone.
However, this does not work as expected in SuperServer, reporting a successful
shutdown while other connections may be still modifying the database file. This
situation is possible under high load.
--
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
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/22/13.
http://pubads.g.doubleclick.net/gampad/clk?id=64545871&iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
