| Article Number | 000033385 |
| Applies To | RSA Product Set: Archer
|
| Issue | When performing Load Runner testing there are numerous HTTP 500 error codes reported in Load Runner and the IIS logs during the performance tests on virtual & physical application servers as the number of simulated users increases. No issues at 10 users test completely fails at 40 to 50 concurrent users with lots of 500 errors. |
| Cause | The http 500 errors are a side effect from individual simulated users in Load Runner attempting to log in concurrently from separate connections or simulated nodes (computer browsers). Archer does not allow a user to be logged in from more then one computer and ends the active session of the first logged in session. This results in a Bad Token error logged in the system level Archer w3wp log. |
| Resolution | The solution to this issue is to configure Load Runner to maintain a single note to users relationship so that a given user is not attempting to login and use Archer at the same time. |
on Jul 19, 2016