Oxygen XML license server

[akshatTR]

Hello, we have setup a license server and oxygen sdk on AWS. Somehow whenever we load the page oxygen keeps connecting to license server every min. Here is the call log. How can we make oxygen connect to license server only once and not repeatedly.

2025-01-20 19:19:06,280 DEBUG [ https-jsse-nio-8443-exec-10 ] org.apache.http.impl.conn.DefaultHttpClientConnectionOperator - Connecting to oxygen-license-server-qa.gcs.int.thomsonreuters.com/10.226.212.83:8080

2025-01-20 19:20:06,497 DEBUG [ Client Keep Alive Thread ] org.apache.http.impl.conn.DefaultHttpClientConnectionOperator - Connecting to oxygen-license-server-qa.gcs.int.thomsonreuters.com/10.226.212.83:8080


FULL LOG FOR ONE CALL is here -


2025-01-20 19:20:06,390 DEBUG [ Client Keep Alive Thread ] org.apache.http.client.protocol.RequestAddCookies - CookieSpec selected: standard
2025-01-20 19:20:06,395 DEBUG [ Client Keep Alive Thread ] org.apache.http.client.protocol.RequestAuthCache - Re-using cached 'basic' auth scheme for http://oxygen-license-server-qa.gcs.int ... s.com:8080
2025-01-20 19:20:06,395 DEBUG [ Client Keep Alive Thread ] org.apache.http.impl.conn.PoolingHttpClientConnectionManager - Connection request: [route: {}->http://oxygen-license-server-qa.gcs.int ... s.com:8080][total available: 3; route allocated: 1 of 4096; total allocated: 3 of 4096]
2025-01-20 19:20:06,396 DEBUG [ Client Keep Alive Thread ] org.apache.http.impl.conn.DefaultManagedHttpClientConnection - http-outgoing-33: Close connection
2025-01-20 19:20:06,396 DEBUG [ Client Keep Alive Thread ] org.apache.http.impl.conn.PoolingHttpClientConnectionManager - Connection leased: [id: 35][route: {}->http://oxygen-license-server-qa.gcs.int ... s.com:8080][total available: 2; route allocated: 1 of 4096; total allocated: 3 of 4096]
2025-01-20 19:20:06,497 DEBUG [ Client Keep Alive Thread ] org.apache.http.impl.conn.DefaultHttpClientConnectionOperator - Connecting to oxygen-license-server-qa.gcs.int.thomsonreuters.com/10.226.212.83:8080
2025-01-20 19:20:06,499 DEBUG [ Client Keep Alive Thread ] org.apache.http.impl.conn.DefaultHttpClientConnectionOperator - Connection established 10.226.213.31:56772<->10.226.212.83:8080
2025-01-20 19:20:06,499 DEBUG [ Client Keep Alive Thread ] org.apache.http.impl.conn.DefaultManagedHttpClientConnection - http-outgoing-35: set socket timeout to 20000
2025-01-20 19:20:06,499 DEBUG [ Client Keep Alive Thread ] org.apache.http.headers - http-outgoing-35 >> GET /oXygenLicenseServlet/license-servlet?action=LIC_REQUEST&serverURL=http%3A%2F%2Foxygen-license-server-qa.gcs.int.thomsonreuters.com%3A8080%2FoXygenLicenseServlet%2Flicense-servlet&sessionid=554E07F1A1179711B300A0D7CA408A3D&hostname=ip-10-226-213-31.ec2.internal&macaddr=0A-FF-D5-43-38-99 HTTP/1.1
2025-01-20 19:20:06,499 DEBUG [ Client Keep Alive Thread ] org.apache.http.headers - http-outgoing-35 >> Accept: application/xml,*/*
2025-01-20 19:20:06,499 DEBUG [ Client Keep Alive Thread ] org.apache.http.headers - http-outgoing-35 >> Accept-Encoding: gzip
2025-01-20 19:20:06,499 DEBUG [ Client Keep Alive Thread ] org.apache.http.headers - http-outgoing-35 >> Host: oxygen-license-server-qa.gcs.int.thomsonreuters.com:8080
2025-01-20 19:20:06,499 DEBUG [ Client Keep Alive Thread ] org.apache.http.headers - http-outgoing-35 >> Connection: Keep-Alive
2025-01-20 19:20:06,500 DEBUG [ Client Keep Alive Thread ] org.apache.http.headers - http-outgoing-35 >> User-Agent: Oxygen XML Editor/27.0
2025-01-20 19:20:06,500 DEBUG [ Client Keep Alive Thread ] org.apache.http.headers - http-outgoing-35 >> Authorization: ****
2025-01-20 19:20:06,502 DEBUG [ Client Keep Alive Thread ] org.apache.http.headers - http-outgoing-35 << HTTP/1.1 200 OK
2025-01-20 19:20:06,503 DEBUG [ Client Keep Alive Thread ] org.apache.http.headers - http-outgoing-35 << Date: Mon, 20 Jan 2025 19:20:06 GMT
2025-01-20 19:20:06,503 DEBUG [ Client Keep Alive Thread ] org.apache.http.headers - http-outgoing-35 << Content-Type: text/html;charset=ISO-8859-1
2025-01-20 19:20:06,503 DEBUG [ Client Keep Alive Thread ] org.apache.http.headers - http-outgoing-35 << Content-Length: 464
2025-01-20 19:20:06,503 DEBUG [ Client Keep Alive Thread ] org.apache.http.headers - http-outgoing-35 << Connection: keep-alive
2025-01-20 19:20:06,503 DEBUG [ Client Keep Alive Thread ] org.apache.http.headers - http-outgoing-35 << Server: Apache-Coyote/1.1
2025-01-20 19:20:06,503 DEBUG [ Client Keep Alive Thread ] org.apache.http.headers - http-outgoing-35 << Cache-Control: private
2025-01-20 19:20:06,503 DEBUG [ Client Keep Alive Thread ] org.apache.http.headers - http-outgoing-35 << Expires: Thu, 01 Jan 1970 00:00:00 UTC
2025-01-20 19:20:06,503 DEBUG [ Client Keep Alive Thread ] org.apache.http.headers - http-outgoing-35 << pragma: no-cache
2025-01-20 19:20:06,503 DEBUG [ Client Keep Alive Thread ] org.apache.http.impl.conn.PoolingHttpClientConnectionManager - Connection [id: 35][route: {}->http://oxygen-license-server-qa.gcs.int ... s.com:8080] can be kept alive indefinitely
2025-01-20 19:20:06,503 DEBUG [ Client Keep Alive Thread ] org.apache.http.impl.conn.DefaultManagedHttpClientConnection - http-outgoing-35: set socket timeout to 0
2025-01-20 19:20:06,503 DEBUG [ Client Keep Alive Thread ] org.apache.http.impl.conn.PoolingHttpClientConnectionManager - Connection released: [id: 35][route: {}->http://oxygen-license-server-qa.gcs.int ... s.com:8080][total available: 3; route allocated: 1 of 4096; total allocated: 3 of 4096]
2025-01-20 19:20:11,261 WARN [ https-jsse-nio-8443-exec-6 ] ro.sync.servlet.config.SessionFilter - Request to /oxygen-xml-web-author/app/images/spinners/blue-spinner.svg was blocked because uses session f3774646-4b2d-46aa-8d62-244a04bdbe24 that was invalidated. Invalidation context: /oxygen-xml-web-author/admin-login
2025-01-20 19:20:11,295 INFO [ https-jsse-nio-8443-exec-17 ] ro.sync.adminauth.userpassword.UserPasswordFormAuthFilter - Successful login to the Administration page from 10.17.66.66

[mihai_coanda]

Hello,

Oxygen Web Author connect to license server every about 90s as part of the license usage custom protocol. This proprietary license usage protocol is not configurable.

Does this behavior cause any issues in your usage of the Web Author with the License Server?

Best Regards,
Michael

[akshatTR]

Hello Micheal,

We are utilizing more licenses instead of the same license being sent every 60 seconds and at one point we run out of licenses and the server starts sending 502 error.

How can we avoid this?

Thank you,
Akshat

[RonaGrant]

Replying for the updates.

[mihai_coanda]

Hello,

The license consumption issue is not cause by the license-use keep alive periodical request. Those requests ensure only the active users consume a floating license and frees consumed license for any users that are no longer being active.

In your case the license consumption most likely is caused by a misconfiguration on the load balancer (API-gateway / reverse-proxy) that interferes with the cookies the Web Author instance uses to track a user session and consume a license for it - this could have multiple side-effects on the editing experience and loss of data in most cases.
When deployed behind a load balancer you should configure your load-balancer with sticky sessions (if you have multiple Web Author instances) and stop if from altering the cookie values as most load balancers append prefixes or suffixes to the cookies passing trough them.

For the Web Author to function as expected its cookies should not be tempered with.

You can read more in the Setting up a Load-Balanced Server [1] topic from our user manual.

Best Regards,
Michael

1. https://www.oxygenxml.com/doc/versions/ ... cing.htmls

[mihai_coanda]

P.S. If this is your production server and you do not have a clear path to clearly identify the issues you can write to us at support@oxygenxml.com with a interval in which we can set up a meeting to help you troubleshoot.