mtls-certificates: Fail on transport, not network level (wrong port)

[Karm]

fixes #40553

The test had been reporting a false negative in HotSpot mode by expecting ConnectException. That exception was not caused by a failed handshake, it was caused by the test trying to talk to the server on a wrong port.

In Native mode, the test framework had the port correct, so it talked to the server and got the correct SSLHandshakeException.

From JDK doc:

java.net.ConnectException
Signals that an error occurred while attempting to connect a socket to a remote address and port.
Typically, the connection was refused remotely (e. g., no process is listening on the remote address/ port).

javax.net.ssl.SSLHandshakeException
Indicates that the client and server could not negotiate the desired level of security.
The connection is no longer usable.

It makes no sense to test a connection refused error on a port nobody listens on. The correct test is to try to trigger a handshake exception while talking to the actual server.

[quarkus-bot]

Thanks for your pull request!

Your pull request does not follow our editorial rules. Could you have a look?

• title should preferably start with an uppercase character (if it makes sense!)

_{This message is automatically generated by a bot.}

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit f0f76dc.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.