Friday 15 March 2013

wso2 - How to restrict the resources within one JVM -


I'm trying with the WSO2 products, and I'm thinking about the scenario where bad code is all CPU Can take time (either dead loop either). I had tried with 2 tenants with WSO2 AS, A and B. And bad effect of A affects B and the response to B's app is delayed or delayed for a long time. Is there a way to restrict the use of a tenant's CPU? Thanks!

Currently you are known as private jet mode for your environment. , Where every tenant gets his own JVM, if you need total separation.

In a shared environment, we have detected the thread which will ensure that important threads will not run for more than the specified period. There is a plan to restrict CPU usage per tenant basis to us. It will be available in future releases.

No comments:

Post a Comment