Free Support Forum - aspose.cloud

Deadlocks problem

Hello.
I am testing your for cloud solution and I have a problem.

Many times I have an error:
Transaction (Process ID 62) was deadlocked on lock | communication
buffer resources with another process and has been chosen as the
deadlock victim. Rerun the transaction.

I make following steps:
1) PUT (with xml data)

http://api.aspose.com/v1.1/words/{templateName}/executeTemplate?folder={templateFolder}&filename={resultFileName}
to generate word document based on template

2) GET
http://api.aspose.com/v1.1/words/{fileName}?format={format}&folder={folderName}
to get generated document in selected format
- format is “docx” or "pdf"

3)DELETE
http://api.aspose.com/v1.1/storage/file/{folder}/{filename}
to delete generated document

For generating only one document this solution works fine.
But when my app is generating more that one document in the same time (more than one user in my web app) or generating one after the other (in short time), this error appear.

Could you help me?

Regards
Lukasz


Hi Lukasz,

We did not find such exception against your account that was created with your email account (starts with lukspam). This account returns "Your have processed '100' documents. Your pricing plan allows only '100' documents." message. Can you please confirm if you are using the same account or using a different account for testing?

Best Regards,

Hi,
yes this account reached 100 docs limit.
But I’m making tests on other free accounts.

For example on this account:
no-exist8@tlen.pl

error appeared at:
- 2/17/2014 10:08 AM
- 2/17/2014 9:57 AM
- 2/17/2014 8:55 AM
and more…

Best Regards,
Lukasz

Hi Lukasz,

This issue was not due to multiple users. It was another issue caused by last database update and a couple of accounts including yours were affected by this change. The issue has been fixed and you should not see this again.

Please let us know if you still see this issue. Sorry for the inconvenience.

Best Regards,

Thank you for your reply.
I’ll check it and I’ll let you know.

Best Regards,
Lukasz