wasp probe leaks memory or consumes high cpu/stops responding

Sometimes you will note (especially in a very busy environment) that the UMP becomes unresponsive and it appears that the wasp probe is using high cpu and/or using more memory than it has been allocated.

Resolution:

This is a result of a misconfiguration in UMP 2.6.x and can be fixed as follows:

1. Make sure you are on UMP 2.6.2, or wasp > 3.04.

2. Edit the file on the WASP server in the folder /nimsoft/probes/service/wasp/webapps/dynamicviews/web-inf/flex/service-config.xml

You will uncomment the following line

<!--

<flex-client>

<timeout-minutes>1</timeout-minutes>

</flex-client>

-->

You should also remove the <!-and --> lines around that text.

so when done it should look like:

<flex-client>

<timeout-minutes>1</timeout-minutes>

</flex-client>

You will need to repeat this for the same file underneath the customdashboard folder as well.