Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MySQL Connector 8.2.0 issue #32940

Open
Charles-II opened this issue May 15, 2024 · 11 comments
Open

MySQL Connector 8.2.0 issue #32940

Charles-II opened this issue May 15, 2024 · 11 comments

Comments

@Charles-II
Copy link

Description

I'm using DBeaver to access MySQL InnoDB clusters version 8.0.36. DBeaver version 22.3.5 with mysql-8.0.31-win64 driver and mysql-connector-j-8.0.29 is working well and I can get the DB table list in few seconds (using filter to reduce table amount). If I upgrade it to newer versions I can open the connection and directly run the queries but as soon as I try to get the filtered table list (through Databases/Tables menu item) a "Load child Items" process starts and the memory occupation grows until the maximum allowed (I have increased it up to 5GB) and then I get "SQL Error [S1000] Java heap Space" error and DBeaver stops working. I think that the issue is related to the new mysql-connector-j-8.2.0 which forcefully replaces the older one. I have also tried to update the mysql driver to version 8.2.0 without success.

DBeaver24.0.4Error.log

DBeaver Version

Community Edition 24.0.4 and 23.3.5

Operating System

Windows 11

Database and driver

Driver mysql-8.0.31-win64
Connector mysql-connector-j-8.2.0

Steps to reproduce

Expand Tables item even with filter applied

Additional context

No problems with DBeaver version 22.3.5, mysql connector mysql-connector-j-8.0.29 and driver mysql-8.0.31-win64
The issue starts with DBeaver 23.x.x up to latest one (all using new mysql-connector-j-8.2.0)

@MashaKorax
Copy link
Contributor

Did you try to use the same version of the mysql-connector-j-8.0.29 and driver mysql-8.0.31-win64?

@MashaKorax
Copy link
Contributor

Please make screenshot of libriries
iScreen Shoter - DBeaver Community - 240516150352

@Charles-II
Copy link
Author

Charles-II commented May 16, 2024

I tried to keep the previous mysql-connector-j-8.0.29 but the DBeaver 24.0.4 install procedure forced me to replace it. If you could explain to me how to install it with the latest DBeaver version I will do a try.

@Charles-II
Copy link
Author

Connector8 2 0_Info
Using DBeaver from version 23.x.x up to 24.0.4

@Charles-II
Copy link
Author

Connector8 0 29
Using DBeaver 22.3.5 (last version which is working well)

@Charles-II
Copy link
Author

MySQL8_driver
MySQL driver version common to all DBeaver versions.

@E1izabeth
Copy link
Member

Please try decreasing the driver version
image

@Charles-II
Copy link
Author

Charles-II commented May 23, 2024

I tried but the problem is still there. I have also tried with the last 24.0.5 version with both connector versions and the problem persists. The last working version is still 22.3.5
EDIT: I have to say that Dbeaver version 22.3.5 uses mysql-connector-j-8.0.29 but with newer DBeaver versions I cannot install connector versions earlier than 8.0.31. So there is still a difference with the connector.

@E1izabeth
Copy link
Member

@Charles-II
Does it reproducible without filtering?

@E1izabeth
Copy link
Member

How many tables do you have in this database?
Have you tried changing -Xmx1024m into -Xmx4096m to increase maximum memory to 4Gb in dbeaver.ini file?

@Charles-II
Copy link
Author

Yes, the problem happens with and without filtering. As reported in the first post I have increased the maximum memory up to 5Gb and the problem is still there. Using the task monitor I can see the memory occupation growing up to the maximum and then I get Java Heap Space error. DBeaver version 22.3.5 works perfectly with and without filtering out tables and even with a 1Gb of maximum memory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants