[BUG] HTTPS connection closes between messages while using HTTP Sender with SSL Enabled

[jdonextgen]

Describe the bug
When using the HTTP Sender connector type with SSL enabled, Mirth Connect closes the TCP connection after each message, requiring the additional overhead of opening a new connection and performing the TLS handshake for each subsequent message. It seems that if the server requires a client certificate (Client Authentication = Require), then the client uses a new port for each message. If the server does NOT require a client cert (Client Authentication = Disabled), then the client uses a single connection.

To Reproduce
Setup steps (if required) and steps to reproduce the behavior:

1. Setup a basic HTTP Sender using the SSL Manager
2. Send to an HTTPS endpoint
3. Turn on the option for Client Authentication = Required
4. Use Wireshark to view the packets

Expected behavior
Using the HTTP Sender connector type with SSL enabled, with Client Authentication = Required, should not close the connection between each message; it should stay connected.

Actual behavior
When using the HTTP Sender connector type with SSL enabled, and Client Authentication = Required, Mirth Connect closes the TCP connection after each message, requiring the additional overhead of opening a new connection and performing the TLS handshake for each subsequent message.

Screenshots
N/A

Environment (please complete the following information):

• OS: [e.g. Linux (CentOS), Windows 10, MacOS]: N/A
• Java Distribution/Version [e.g. OpenJDK 11, Java 8 (201)]: N/A
• Connect Version [e.g. 3.8.0]: MC 4.2.0

Workaround(s)
N/A

Additional context
N/A

[jdonextgen]

Fix has been committed and will be available in our Mirth Connect 4.5.2 release.