Hi,
I noticed a strange behaviour when accessing the rest endpoint massivly parallel. E.g. a lot of users want to download a document. On a certain number OpenKM starts to hang and the threads are working on 100% without returning.
I don't know if it is a tomcat configuration problem or another problem inside OpenKM itself.
To show the problem, I attached a stress test. Even with a small number of (e.g.) 1000 clients I'm able to stuck the OpenKM Demo instance so that no further usage is possible. Interessting is, that the system is running fine again when the test is aborted.
The test calls getContent for a specific document with a certain number of clients.
When taking a threaddump it shows that the system is hanging in DocumentService.java:147 -> IOUtils.copy(...) without returning.
Any advices?
Maybe you can use the test class on your demo instances.
I noticed a strange behaviour when accessing the rest endpoint massivly parallel. E.g. a lot of users want to download a document. On a certain number OpenKM starts to hang and the threads are working on 100% without returning.
I don't know if it is a tomcat configuration problem or another problem inside OpenKM itself.
To show the problem, I attached a stress test. Even with a small number of (e.g.) 1000 clients I'm able to stuck the OpenKM Demo instance so that no further usage is possible. Interessting is, that the system is running fine again when the test is aborted.
The test calls getContent for a specific document with a certain number of clients.
When taking a threaddump it shows that the system is hanging in DocumentService.java:147 -> IOUtils.copy(...) without returning.
Any advices?
Maybe you can use the test class on your demo instances.
Attachments
(976 Bytes) Downloaded 1124 times