NeoLoad 7.11.1 uses log4j 2.11.2 so IT IS affected. There is a new 7.11.2 version available that fixes the vulnerability.
You can check your NeoLoad installation by looking...
We're connected to a SaaS instance of Neoload web. However sometimer when running tests it won't connect as it has timed out.
Is it possible to change the timeout setting?
I do not think we can increase that timeout and do you think that it will work if we increase it knowing that it failed after 30s which is already a lot. And the question is...
We are trying to record an application that uses comet push notifications, in particular XMLHttpRequest long polling. The push module of Neoload 5.1 does not seem to pick it up...
Normally if NeoLoad identifies PUSH mechanism it should create a simplified virtual user with fork and PUSH messages.
So i guess it was not able to identify the PUSH mechanism...