000033385 - HTTP 500 errors during performance testing in RSA Archer

Document created by RSA Customer Support Employee on Jul 19, 2016Last modified by RSA Customer Support on Sep 18, 2019
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000033385
Applies ToRSA Product Set: Archer
 
IssueWhen 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 and physical application servers as the number of simulated users increases. No issues at ten users test completely fails at 40 to 50 concurrent users with lots of 500 errors.
CauseThe 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). RSA 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.
ResolutionThe solution to this issue is to configure Load Runner to maintain a single node-to-user relationship so that a given user is not attempting to login and use RSA Archer at the same time.

Attachments

    Outcomes