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 92500 - can't access derby "sample" database
Summary: can't access derby "sample" database
Status: VERIFIED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: Derby (show other bugs)
Version: 5.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: Andrei Badea
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-14 12:58 UTC by bigbarnsmell
Modified: 2007-02-28 14:59 UTC (History)
0 users

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 bigbarnsmell 2007-01-14 12:58:28 UTC
In NetBeans 5.5 with Derby 10.2.2 when trying to access the database “sample,” I
received the following set of error messages:

Exception in thread "DRDAConnThread_3" java.lang.NoClassDefFoundError:
java/sql/SQLClientInfoException 
        at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source) 
        at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) 
	at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source) 
        at org.apache.derby.impl.drda.Database.makeConnection(Unknown Source) 
     at
org.apache.derby.impl.drda.DRDAConnThread.getConnFromDatabaseName(Unknown Source) 
	at org.apache.derby.impl.drda.DRDAConnThread.verifyUserIdPassword(Unknown Source) 
        at org.apache.derby.impl.drda.DRDAConnThread.parseSECCHK(Unknown Source) 
        at org.apache.derby.impl.drda.DRDAConnThread.parseDRDAConnection(Unknown
Source) 
	at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unknown Source) 
        at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)

This means virtually nothing to me.  With all due thanks in advance, can anyone
help?  I have already uninstalled and re-installed the IDE to no avail.
Comment 1 Andrei Badea 2007-01-16 21:07:55 UTC
It seems 10.2.2 requires JDK 1.6 because of the JDBC 4.0 drivers, so please use
that JDK version.
Comment 2 Andrei Badea 2007-01-17 19:33:22 UTC
From reporter by private e-mail:

My apologies for not having noted that I am using JDK 1.6.  The problem remains.
Comment 3 bigbarnsmell 2007-02-20 18:05:20 UTC
The problem was a jdk 1.6.0 release candidate was being used.  With jdk 1.6.0
the problem goes away
Comment 4 Lukasz Grela 2007-02-28 14:59:05 UTC
v.