DateTime: 29/09/2023 9:45 am - 10:00 am
PDF files and Doc To Pdf were failing between this interval.
It is not the first time this happens, could you give us some advice on the issue?
Hello Alexey,
We use the below actions, from the extension AsposeWordsEnhanced, on-premises.
The underlined actions were giving durations much higher than expected.
Also, is there any outside connection from your side, on the MergeToPdf API, that could cause these issues?
Thank you,
PPL Run Team
@PTDLPPLRunTeam AsposeWordsEnhanced is not part of Aspose.Words API. Do you use Aspose.Words in your implementation of AsposeWordsEnhanced service? If so could you please share code you use and documents that cause the problem, we will test the scenarios on our side and provide you more information.
We use Aspose.Words and Aspose.PDF API’s - both on version 23.5.0. Maybe this services fall under the second API.
Also we are using this code:
This was not related to one specific document. Can this be related with the PDFlicense verification on your servers? We could see a degradation of response on both services that checks the licenses at the timestamp provided.
@PTDLPPLRunTeam As I can see, the license is applied each time the method is called. This is not required, the license should be applied only once per application domain. For example, you can apply the license on application start or in a static constructor of the main class.
Also, you are using metered license, which makes call to our server to verify license. Too many request to the license verification service might cause rejection of the further requests.
Hi Support, thanks for reply.
So you confirm, that by using the metered license, there is a call to your (aspose) servers? Can you disclose the url being called by the dll please. Also can you confirm if there were any rejection from your end at that interval (29th sep between 9.45am and 10am)? When you say “too many requests” - how many are we talking about and how can we work around that in heavy loaded apps, wondering? Besides the license call, can you share if there is any other call from the dll / library (Aspose.pdf or related) yo your server or outside of our domain / network? Thanks.
Aspose.Words makes a call to https://purchase-api.dynabic.com/v1.2 when metered license is applied.
No, there is no other external calls from Aspose libraries.
Regarding other questions I will consult with our metered license team.
@PTDLPPLRunTeam There was a downtime on our server on 29 September due to a Windows update that caused failure of our services. Most likely this caused problems on your side.
Thanks for the reply. If that api (metered license) is down, does it mean we can’t serve our requests - can we minimize the number of calls to that api? Also, is there a way to know possible downtimes, is that tracked somewhere?
You can apply the license once per application domain to avoid redundant calls to the metered licensing service.
You can track status here https://status.containerize.com/
Thanks for the details. Can you please confirm, if the metered license api is down, that affects us and our ability to serve the end users? Also, in a context where multiple licenses are at play, is that feasible, applying the license per domain?
@PTDLPPLRunTeam Currently metered licensing service is working properly.
It is correct to apply the license once per application domain regardless how many licenses are used in the application. You should simply apply the license for each Aspose product used in the application.
Hi again, can you confirm if the api is down that will affect our ability to serve requests?
Also, today we had several issues with the api, can you tells us why is the api so unstable? And what can we expect in the future? Is this going to be normal?
@PTDLPPLRunTeam There ware issues with metered license service today, but they have been fixed and now works fine.
We will do our best to avoid the problem in the future. Please accept our apologies for your inconvenience.