Issue 76555 - Crashes connecting to ApacheDerby dbs (both in embedded and client-server environment)
Summary: Crashes connecting to ApacheDerby dbs (both in embedded and client-server env...
Status: CLOSED DUPLICATE of issue 74732
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: recent-trunk
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: dbaneedsconfirm
QA Contact: issues@dba
Depends on:
Reported: 2007-04-20 18:28 UTC by Ariel Constenla-Haile
Modified: 2013-08-07 15:45 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description Ariel Constenla-Haile 2007-04-20 18:28:51 UTC
I could connect to an Apache Derby database (both in an embedded and a
client/server environment). OOoBase shows the database tables
when I touch the "Tables" icon on the left panel. I could run SQL
commands with the Tools - SQL dialog. I could execute queries with

But OOoBase crashes the whole application in the following cases:

* I try to open a table to edit its structure, or insert data (double
click on the table icon or context menu, and OOo crashes after a few
* I try to execute a query passing through the parser (after executing
the query in native sql mode, I press - set it unselected - the native
sql icon in order to use OOo PARSER, I press the execute query icon, and
OOo crashes after a few seconds)
* I try to use any wizard

In all this cases, OOo uses 100% of the CPU, and after a few seconds,
crushes completely.

I'm using
* the current version OOo 2.2 680m14 (Build:9134)
* WinXP Pro 5.1
* AMD Athlon 64 X2
* RAM 1 gb

Derby configuration, classpath, drivers, connection URL, they all are
set properly (I tested them with dif. apps, for ex. the NetBeans IDE 5.5, and
there is no problem at all).

PS: the connection pool is disabled (I mention it because sometimes, in
other issues, it seems to be its fault)
Comment 1 Frank Schönheit 2007-04-20 19:27:23 UTC
it's a duplicate of one of the duplicates of issue 74732. An no, connection
pooling isn't the reason, though in case of one DB (embedded HSQL), connection
pooling is needed to trigger this bug.

*** This issue has been marked as a duplicate of 74732 ***
Comment 2 Frank Schönheit 2007-04-20 19:29:29 UTC
closing duplicate