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 55124 - NetBeans can't connect to PointBase
Summary: NetBeans can't connect to PointBase
Status: RESOLVED WORKSFORME
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Andrei Badea
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2005-02-17 10:06 UTC by Petr Blaha
Modified: 2005-10-08 17:39 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
stack trace (7.46 KB, text/plain)
2005-02-17 10:07 UTC, Petr Blaha 		Details
My messages.log file (20.90 KB, text/plain)
2005-02-24 13:19 UTC, Petr Jiricka 		Details
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 Petr Blaha 2005-02-17 10:06:27 UTC 
[Build 20050216]
RANDOM
Steps:
1) try to connect to local PointBase db
2) specify user/passwd
3) it seems that connection was established.
However, no tables are listed under Table node. In
NetBeans log is attached exception.
Comment 1 Petr Blaha 2005-02-17 10:07:22 UTC 
Created attachment 20396 [details]
stack trace
Comment 2 Radko Najman 2005-02-18 12:41:49 UTC 
Cannot reproduce. From the stack trace it seems like a network or
driver problem
Comment 3 Petr Jiricka 2005-02-24 13:18:24 UTC 
I just got some exceptions that look related - this does not work for
me either. Attaching my IDE log file.
Comment 4 Petr Jiricka 2005-02-24 13:19:12 UTC 
Created attachment 20501 [details]
My messages.log file
Comment 5 Andrei Badea 2005-10-07 17:55:44 UTC 
I recall seeing this issue, but never since the integration of the changes in
the Database Explorer caused by the introduction of the DB  Explorer API. Looks
like a threading issue.

Closing, reopen if you encounter this again.
Comment 6 Petr Blaha 2005-10-08 17:39:41 UTC 
Andrei, I filed similar issue #66010 that is 100% reproducible on my comp. The
behaviour is similar as for this issue. Can you look on this and mentioned issue?