Details
-
New Feature
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
-
All
Description
Fixed an issue in ConnectionHelper where Socket connections sometimes failed. Socket connections now try all possible IP addresses, not just the first one.
When a host has multiple IP resolution results, especially when the results include both IPv4 and IPv6 addresses, this change can help connect to the correct IP.
For example, if the server is listening on ::1 and the client uses localhost to connect, by default, it will only attempt to connect to 127.0.0.1
I create a PR(https://github.com/mariadb-corporation/mariadb-connector-j/pull/196) to fix issue