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.
Summary: | Opening a 2nd connection to an Oracle DB fails | ||
---|---|---|---|
Product: | db | Reporter: | smil <smil> |
Component: | Code | Assignee: | Andrei Badea <abadea> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | pjiricka |
Priority: | P3 | ||
Version: | 5.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
smil
2006-02-03 15:32:49 UTC
Additional info: The same can be experienced on NB 4.1. SunOS fee 5.9 Generic_117171-15 sun4u sparc SUNW,Sun-Fire-V250 java version "1.4.2_04" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05) Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode) Yes, you are right, we are using a different classloader for every connection. We already plan to fix it. Thanks for filing the issue! I'm afraid this is too hard and time-consuming to fix for 5.5. It requires caching class loaders, or actually creating a single one, and it is not trivial to implement correctly. ... but it was not very difficult to implement the workaround in issue 76922, which mitigates the problem quite significantly. *** This issue has been marked as a duplicate of 76922 *** |