Aspose on premise approach giving red message boxes in converted pdf

Aspose.Words Cloud Product Family
21

Any idea, on which port the service runs on pod? Baceause that would be also be required when I set up the liveliness probe

22

The application itself uses 80 ports, which port you map to it, depending on your docker-compose or whatever method you use.

1 Like
23

Hey, Just wanted to ask one thing like I am trying to implement a liveliness probe so as to automatically restart container. But seems like, the aspose words docker image, does not have any curl, jq installed. Is it possible to include these in the image?

24

i’m afraid we do not have such plans as we plan make images as small as possible

25

Hi,

We received this issue in production again! When I triggered the URL, we got this:

{
“Name”: “Aspose.Words Cloud API”,
“Version”: “24.12.0”,
“AdditionalInfo”: [
{
“Key”: “ConsumptionCredit”,
“Value”: “57744”
},
{
“Key”: “ConsumptionQuantity”,
“Value”: “23667.3795”
},
{
“Key”: “IsMeteredLicensed”,
“Value”: “True”
}
],
“RequestId”: “a519cfcc-a92a-4534-ad47-0730232db191”
}

We are loosing business due to this and is a very serious concern to us as this is happening intermittently a lot of times. Please fix it from aspose side asap.

Please note that this was observed around 5:08 pm (IST)

26

Sorry for the inconvenience. I shared your error with the billing team.

27

Hi team. We are running two instances of aspose-words as on premise. We started intermittently getting the issue that we started observing aspose red mark. I observed that one of the pods is not giving checkMeteredLicense in the health URL response:

{
“Name”: “Aspose.Words Cloud API”,
“Version”: “25.3.0”,
“RequestId”: “9c8cc7a4-1229-4a75-bcd8-882eb5e156f9”
}

{
“Name”: “Aspose.Words Cloud API”,
“Version”: “25.3.0”,
“AdditionalInfo”: [
{
“Key”: “ConsumptionCredit”,
“Value”: “67277”
},
{
“Key”: “ConsumptionQuantity”,
“Value”: “9061.0220”
},
{
“Key”: “IsMeteredLicensed”,
“Value”: “True”
}
],
“RequestId”: “7f218553-5683-4d46-9f20-a79cc6a0b3ae”
}

Can you please comment on this?

28

It says that the license is okay, I will ask the billing team to check the license

29

If you see, I pasted two json response. In one of them:

{
“Name”: “Aspose.Words Cloud API”,
“Version”: “25.3.0”,
“RequestId”: “9c8cc7a4-1229-4a75-bcd8-882eb5e156f9”
}

We did not get this key. That’s what I want you to check

30

Yes, I see I shared that info with the billing team, so they will try to replicate this issue with multiple containers running with the same keys

1 Like
31

Hi, This happened in production as well and still some of our instances are running while others are giving red mark. Please check this on priority is this is P0 for us.

32

Sure, I shared all the info with the billing team. I hope it will be resolved ASAP.

33

{
“Name”: “Aspose.Words Cloud API”,
“Version”: “25.3.0”,
“RequestId”: “81936ace-6e4f-434a-94cd-162d7e0ac33a”
}

We again got this in production!!

Some of the pods are giving above response and failing to convert document to pdf. We already reported this earlier. What is the solution and root cause for this?

34

It’s hard to say what is wrong with the configuration or connection, as we can’t find any issues with the billing service. As far as I know, the billing algorithm is going to be updated in the upcoming release

35

Our on premise apis are facing water mark issues again!!!

36

I shared that info with the billing team, other product also faced the same issue with billing, they are investigating issue.