This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
To reproduce the issue: - Start the ide and create a database connection. - The node appears in the runtime panel. - Simulate a crash via Ctrl+C (abnormal exit). - Restart the ide. The database connection node is not shown in the runtime tab. (It would have if the exit was done normally). The database connection is only an example and this is not specific to db module. In general, are the settings and such stored only at exit time? Is there an api that can force an immediate save and flush (either for that node or for all such settings that may be unsaved)? Or is the save done at regular intervals? If so is the interval customizable? A system hang can occur due to various reasons that are not even related to the ide and recreating the settings manually again should be avoided if possible. (If the ide stores the nodes etc at regular reasonable intervals, that of course is a reasonable implementation).
Settings infrastructure persists modified setting asynchronously with the delay of 2000ms after it was modified. That means that any subsequent changes are batched. However skimming code of db module it looks that they are persisting settings on their own so they should answer this question.
This issue has been already fixed for NetBeans 4.0 in db module.
VERIFIED