-
Notifications
You must be signed in to change notification settings - Fork 977
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
ProxySQL works in CLI, but not with Java client #847
Comments
Hi Olaf, |
@renecannao I created some more pcap files. Can I e-mail you the dumps? |
Absolutely yes! |
You've got mail ;) |
@olafz : thank you for the pcap files.
It was already reported in #718 that Perl does that, but I wasn't expecting also Java using the same approach. Thanks |
@renecannao Thanks for figuring this out! Since it's no major change but a bugfix, I'd say to put the fix in 1.3.2. The sooner, the better ;) |
Ack! :) |
#718 applied to v1.3.2-dev |
Any update on the v1.3.2 release? |
Version v1.3.2 is now released. |
Hi @renecannao, thanks for the release! I immediately tried it, but unfortunately this issue is not solved. In fact, it's even worse. I created a new issue for that: #857 |
We have a straight forward setup with two backend servers, each containing 1 schema:
presdb_TE1002 (on server 10.120.10.31) and trojka_d (on server 10.120.8.2). There exists one user that can read from both. On both backend servers,
lower_case_table_names = 1
is set.The version of ProxySQL is 1.3.1 and the setup is as follows:
The setup works, as connecting to ProxySQL using the cli shows:
Now, when trying to do the same with a Java client, we get a
SQL ERROR CODE: 1044, message: Access denied for user 'trojka_ro_d'@'10.120.%' to database 'presdb_te1002'
on the last step.We've written a simple java client that connects, changes schema and show the tables.
We've created TCPdump(s) to show what happens:
First (works)
Second (fails)
If you're interested in the raw pcap file, let us know.
The text was updated successfully, but these errors were encountered: