MySQL Aurora failover ends up on reader when using custom domain

[szhnet]

Describe the bug

#386 The problem still exists.

A jdbc url like this: jdbc:aws-wrapper:mysql://[custom-domain]:3306/db?characterEncoding=utf-8&clusterInstanceHostPattern=?.[clusterid].us-east-1.rds.amazonaws.com&wrapperLoggerLevel=ALL

In the log there is something like this
The driver is unable to track this opened connection because the instance endpoint is unknown: '[custom-domain]'

java.sql.SQLException: Running in read-only mode

Expected Behavior

The failover should end up on the writer node.

What plugins are used? What other connection properties were set?

Default plugins are used.

Current Behavior

The connection ends up on the reader instead of the writer.

Reproduction Steps

See description.

Possible Solution

No response

Additional Information/Context

No response

The AWS Advanced JDBC Driver version used

2.5.4

JDK version used

11

Operating System and version

Linux

[aaron-congo]

Hi @szhnet,

Thanks for reaching out and raising this issue. We'll take a look at this and keep you updated as we investigate. Thank you for your patience!