Issue 75852 - JDBC access to MySQL appears to be broken
Summary: JDBC access to MySQL appears to be broken
Status: CLOSED DUPLICATE of issue 74732
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.2
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: dbaneedsconfirm
QA Contact: issues@dba
: 76110 (view as issue list)
Depends on:
Reported: 2007-03-29 10:52 UTC by osavill
Modified: 2013-08-07 15:45 UTC (History)
2 users (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 osavill 2007-03-29 10:52:22 UTC
I am using OOo with the MySQL JDBC driver to connect to a database on a 
different machine on our intranet. I can configure the connection fine and I 
can also connect to the database. Selecting the Tables button accurately shows 
the tables within the database. Double clicking on a table causes the following 
The application becomes unresponsive, about 30 seconds later there is a flurry 
of disc activity but the application remains unresponsive. Some time later, 
maybe up to a minute the application simply dissappears, taking the system tray 
icon with it. There are no OOo has crashed type dialogs the application simply 

If the disc activity was a crash log then I'll attach it, but please tell me 
where it dumps this kind of data.

The same ODB file opens and works just fine in OOo 2.1
Comment 1 Mechtilde 2007-03-29 12:03:07 UTC
I can't see this problem in 2.2 RC4 under Debian

Which OS Do you use? Where do you get your JDBC driver from? which version?

Which mysql version do you use?
Comment 2 osavill 2007-04-01 21:07:12 UTC
Sorry, filed the report while at work - had to hurry !

I was using Windows XP (don't know which service pack but it's going to be up to
date), MySQL 5 (I can find out exactly which version tomorrow) and MySQL's own
JDBC driver (version Connector/J 5.0.5).
Comment 3 Frank Schönheit 2007-04-02 12:06:06 UTC
cannot reproduce with MySQL 5, Connector/J 5.0.5, WinXP SP2, Sun JRE 1.6.0, OOo 2.2.
Comment 4 osavill 2007-04-02 16:11:43 UTC
Using MySQL 5.0.27-community-nt and Sun's JRE 1.6

Will try again with 2.2 release...
Comment 5 osavill 2007-04-02 16:35:46 UTC
Downloaded the final 2.2 release and it's exactly the same.

OOo 2.1 with exactly the same setup works just fine. 

Are there any diagnostics that can be switched on ?
Comment 6 osavill 2007-04-02 16:36:46 UTC
Changed release field to indicate that issue persists in final release code
Comment 7 Frank Schönheit 2007-04-02 19:56:25 UTC
From the symptoms you describe, it is possible that this is a duplicate of issue
contains libraries from a OOo 2.2, plus a fix for issue 74732, for Windows resp.
Linux. If you find a minute, please try those whether they fix your problem. As
usual, don't forget to backup the old libs, don't use this in production, and
the like ...
Comment 8 Frank Schönheit 2007-04-05 07:09:35 UTC
*** Issue 76110 has been marked as a duplicate of this issue. ***
Comment 9 jjmckenzie 2007-04-06 04:45:49 UTC
Confirming.  This has been reported on the Mac OS X mailing list.  It appears
that JDBC connections to either a local or remote database do not work for 2.2.0
for MySQL.  This is also broken for JDBC built specifically for Mac OS X.

James McKenzie
Comment 10 Frank Schönheit 2007-04-10 07:18:53 UTC
Ping. Anybody who has the chance to try the preliminary fix as mentioned above?
Comment 11 drewjensen.inbox 2007-04-15 15:33:30 UTC
I was able to duplicate the problem on my machine:

XP, JRE 1.6, 2.2 Stable, MySQL 5.0.37 ( localhost ), JDBC 5.0.3

After replacing the file dbtools680mi.dll with the patched version the problem
has been resolved.
Comment 12 Frank Schönheit 2007-04-16 07:19:12 UTC
Thanks a lot. Marking as duplicate of issue 74732 then.

*** This issue has been marked as a duplicate of 74732 ***
Comment 13 Frank Schönheit 2007-04-16 07:22:00 UTC
closing duplicate