version 2.5.6 not able to handle database url's with a trailing .

[parkerirving45]

Describe the bug

The previous version of the driver 2.3.5 was able to properly handle a trailing . Now the hostSpec is different https://github.com/aws/aws-advanced-jdbc-wrapper/blob/main/wrapper/src/main/java/s[…]on/jdbc/plugin/readwritesplitting/ReadWriteSplittingPlugin.java
with the older version of the driver, the hostSpec is the same whether or not the is a trailing . --> the trailing . seems to be parsed away
with the newer version of the driver, the hostSpecs are different --> the trailing . isn't parsed away (which I think is what causes issues)

Expected Behavior

I expected the hostSpec to be the same whether or not there is a trailing .

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

readwritesplitting

Current Behavior

It is unable to establish a connection to the reader instance when there is a trailing . and instead sends all traffic to the writer.

Reproduction Steps

Configure your database url with a trailing . at the end and then try to connect to a reader instance of that database using the readwritesplitting plugin.

Possible Solution

Change how the host is parsed to ignore trailing .

Additional Information/Context

No response

The AWS Advanced JDBC Driver version used

2.5.6

JDK version used

11

Operating System and version

OSX

[aaron-congo]

Hi @parkerirving45,

Thanks for submitting this ticket. Can you provide us with more information about why the URL has a trailing period that you would like stripped away?

[parkerirving45]

@aaron-congo a database with a trailing dot is a valid DNS so it should be handled fine and was previously handled fine in version 2.3.5 by the driver

[aaron-congo]

Hi @parkerirving45,

We have just merged in a fix. Could you kindly checkout our snapshot build and let us know if the issue still persists? The artifact you're looking for should be aws-advanced-jdbc-wrapper-2.5.7-20250514.184536-21.jar.

Thank you!

[parkerirving45]

Hey @aaron-congo we have a ticket in our backlog to test this out I will let you know when we get to testing it

[karenc-bq]

Hi @parkerirving45, the fix is now available in version 2.6.0. We will be closing this ticket now, please let us know if you run into this or any other issues again. Thank you again for raising this issue to us.