Default clusterId doesn't include user about aws-mysql-jdbc HOT 2 CLOSED

Ah ok, dang I thought I was on to something since I saw HostInfo has user and password variables.

We are using 1.1.4 and notice the issue when a connection drops and reconnects, we can trigger it by failing over the db.

Multiple pools, completely different class instances so I thought it would have to be something shared like the topoogy cache.

We've got an support case open about it, so I'll close this issue since the user/pass aren't used and troubleshoot further there.

Thanks!

from aws-mysql-jdbc.

Hi @b1tninja,

Thanks for reaching out and raising this issue.

We'll keep you updated as we investigate.

In the meantime, I have a few questions:

• What version of the driver are you using? In the latest version of the driver, the topology cache keeps the host, port, and other properties that come from the topology query. Any connection-specific properties (including the username, password, etc.) should not be in the topology cache. The connection specific properties used to be stored in the topology cache, but this was changed in version 1.1.8.
• How is your connection pool configured and what properties are being used? Are you using multiple connection pools?
• If possible, could you provide driver logs? They can be enabled as seen here.

Thank you!

from aws-mysql-jdbc.