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 219767 - IllegalStateException: Unable to Connect to database : DatabaseConnection[name='jdbc:oracle:thin:@192.168.210.49:1521:XE [MEDEA on MEDEA]']
Summary: IllegalStateException: Unable to Connect to database : DatabaseConnection[nam...
Status: RESOLVED DUPLICATE of bug 219910
Alias: None
Product: db
Classification: Unclassified
Component: Show Data (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-09 14:41 UTC by medeag
Modified: 2012-10-12 14:06 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 193295

Attachments
stacktrace (1.25 KB, text/plain)
2012-10-09 14:42 UTC, medeag 		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 medeag 2012-10-09 14:41:52 UTC 
Build: NetBeans IDE Dev (Build 201210070002)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.1-b03, Java(TM) SE Runtime Environment, 1.7.0_05-b06
OS: Windows 7

User Comments:
medeag: running query




Stacktrace: 
java.lang.IllegalStateException: Unable to Connect to database : DatabaseConnection[name='jdbc:oracle:thin:@192.168.210.49:1521:XE [MEDEA on MEDEA]']
   at org.netbeans.modules.db.dataview.output.SQLExecutionHelper$1Loader.run(SQLExecutionHelper.java:132)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
   at java.util.concurrent.FutureTask.run(FutureTask.java:166)
   at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1454)
   at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2036)
Comment 1 medeag 2012-10-09 14:42:10 UTC 
Created attachment 125638 [details]
stacktrace
Comment 2 Jaroslav Havlin 2012-10-12 14:06:06 UTC 
Duplicate of 219910. I see that you are able to reproduce the bug.
Please, if you can provide additional information, it would be helpful. Thanks.

*** This bug has been marked as a duplicate of bug 219910 ***