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.

Bug 51615 - Information loss (like database connections) on crash and restart.
Summary: Information loss (like database connections) on crash and restart.
Status: CLOSED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: Sun All
: P3 blocker (vote)
Assignee: Radko Najman
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-18 00:05 UTC by Unknown
Modified: 2007-04-02 20:17 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2004-11-18 00:05:05 UTC
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).
Comment 1 David Konecny 2004-11-18 12:59:46 UTC
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.
Comment 2 Radko Najman 2004-12-01 11:11:10 UTC
This issue has been already fixed for NetBeans 4.0 in db module.
Comment 3 Martin Schovanek 2005-11-21 10:02:13 UTC
VERIFIED