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 151497 - About 10 the same error messages appear by attempt to connect to stopped Java DB
Summary: About 10 the same error messages appear by attempt to connect to stopped Java DB
Status: RESOLVED DUPLICATE of bug 151903
Alias: None
Product: db
Classification: Unclassified
Component: Derby (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks: 152765
  Show dependency tree
 
Reported: 2008-10-27 16:55 UTC by Roman Mostyka
Modified: 2009-07-01 08:36 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Mostyka 2008-10-27 16:55:50 UTC 
1. Start Java DB.
2. Stop Java DB and try to establish some Java DB connection (during stopping).

Result: NetBeans hungs up for sume time and then about 10 the same error messages appear.
Comment 1 John Baker 2008-10-29 20:27:47 UTC 
This doesn't look like a bug to me.
It doesn't make sense to make a connection while shutting down

For me, Java DB shuts down so quickly that I don't have time to try to make a connection
Comment 2 Roman Mostyka 2008-10-30 18:37:35 UTC 
DB can be shutdown remotely. But 10 the same error message looks like IDE can't properly process a problem.
Comment 3 John Baker 2008-10-31 01:34:47 UTC 
Despite, "DB can be shutdown remotely" I still don't think this is a bug since it's a weird use case to try to
connect to a database that is shut down.

Besides you have to be really quick to try to connect since Java DB shuts down so quickly
Comment 4 Roman Mostyka 2008-10-31 13:17:51 UTC 
It is probably not so often reproducible issue, but it exists.
And it seems that IDE can't handle error quite good, since it throws about 10 the same error messages, I guess one is
enough. ;)
And this problem probably can occur not only if Java DB is shutdown, this case is just I can reproduce.
Comment 5 Jiri Rechtacek 2009-07-01 07:57:18 UTC 
Reassigned to new owner.
Comment 6 Jiri Skrivanek 2009-07-01 08:36:18 UTC 

*** This issue has been marked as a duplicate of 151903 ***