Issue Details (XML | Word | Printable)

Key: CORE-3622
Type: Improvement Improvement
Status: Reopened Reopened
Priority: Critical Critical
Assignee: Unassigned
Reporter: F.D.Castel
Votes: 2
Watchers: 4

If you were logged in you would be able to see more operations.
Firebird Core

Classic: Stopping Windows Service leaves one or more instances of fb_inet_server.exe running

Created: 07/Oct/11 09:18 AM   Updated: 10/Oct/11 10:06 AM
Component/s: Engine
Affects Version/s: None
Fix Version/s: None

Environment: Windows Server 2003 / SP2 / x86

 Description  « Hide
Sometimes stopping Windows Service on Firebird Classic 2.5.0 can leave one or more instances of fb_inet_server.exe running.

This is highly undesirable, since it could lead one to think the database file isn't in use as the service status is "Stopped". A database file copy or file-level backup in this state can corrupt the database (actually this DID occur once with me, and that's why I flagged this issue as "critical").

The correct behavior should be:
- (preferred) The service STOPS, no more instances left running and all database files closed ; *OR*
- The service DON'T STOP, returning an error message.

Currently, running a

    taskkill /im fb_inet_server.exe /f

can surely kill every zombie process, but I don't know how harmful this can be.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no subversion log entries for this issue yet.