Connection issues after deployed Oxygen XML Web Author has been running for some time

[trentono]

Hello,
We have been experiencing issues with our deployed Oxygen XML Web Author, where a day or two after deploying we start seeing connection timeouts (both when trying to connect to our license server, and also when trying to connect to a URL for a custom plugin). Re-deploying the Oxygen XML Web Author seems to resolve the connection issues, but they eventually reappear. These connection issues seemed to appear soon after upgrading from v24.1.0 to v26.0.0.

Is there something we're maybe missing in the way we're handling connections that might cause this? I could see that possibly being an issue with our custom plugin, but it doesn't seem like we should be having an issue with connections to the license server.

The specific errors we see in the logs are (specific hosts and IPs redacted):

For the plugin:
org.apache.http.impl.execchain.RetryExec - I/O exception (org.apache.http.conn.ConnectTimeoutException) caught when processing request to {s}->https://xxxxx.xxx.xxxxxxx.com:443: Connect to xxxxx.xxx.xxxxxxx.com:443 [xxxxx.xxx.xxxxxxx.com/55.555.555.55, xxxxx.xxx.xxxxxxx.com/55.555.555.56, xxxxx.xxx.xxxxxxx.com/55.555.555.57] failed: Connect timed out

For the license server:
org.apache.http.impl.execchain.RetryExec - I/O exception (org.apache.http.conn.ConnectTimeoutException) caught when processing request to {}->http://license-server.xxx.xxxxxxx.com:8080: Connect to license-server.xxx.xxxxxxx.com:8080 [license-server.xxx.xxxxxxx.com/55.555.555.58, license-server.xxx.xxxxxxx.com/55.555.555.59, license-server.gcs.xxx.xxxxxxx.com/55.555.555.50] failed: Connect timed out
and then:
ro.sync.ecss.webapp.d.u - Failed to login user user-7124572024191125852: Could not connect to license server: Connect to license-xxx.xxxxxxx.com:8080 [license-server.xxx.xxxxxxx.com/55.555.555.58, license-server.xxx.xxxxxxx.com/55.555.555.59, license-server.gcs.xxx.xxxxxxx.com/55.555.555.50] failed: Connect timed out (http://****@license-server.xxx.xxxxxxx. ... 6-66-66-66)

Also, possibly related, we also see a lot of errors like this when trying to connect to the host our plugin accesses (where the alternative subject names aren't anything related to the host we're trying to access):
org.apache.http.impl.execchain.RetryExec - I/O exception (javax.net.ssl.SSLPeerUnverifiedException) caught when processing request to {s}->https://xxxxx.xxx.xxxxxxx.com:443: Certificate for <xxxxx.xxx.xxxxxxx.com.com> doesn't match any of the subject alternative names: [yyyyyyy.yyyy.yyyyy.com]

Any suggestions would be welcome.

Thanks,
Trent Olson

[cosminef]

Hello,

When security is enabled in Oxygen XML Web Author, mapping from the DNS name of an external server (for example, the License Server) to its IP address are cached indefinitely. If the server is set up to have a dynamic IP address, Oxygen XML Web Author might attempt to use an outdated IP address, resulting in a failed connection.
If this is also your use case, you can try the workaround here [1].

[1] https://www.oxygenxml.com/doc/versions/ ... itely.html

Best,
Cosmin