Submit a ticketCall us
Home > Success Center > Web Performance Monitor (WPM) > WPM - Knowledgebase Articles > WPM recordings that include AngularJS may fail

WPM recordings that include AngularJS may fail

Updated January 8, 2018

Overview

This article provides a workaround to try if WPM recordings that include Angular JS and the Route AngularJS service fail during playback. 

Environment

  • WPM 2.2 and later

Cause 

The AngularJS structural framework lacks required resources, which are consumed by WPM worker processes. 

Resolution

SolarWinds recommends the following workarounds for WPM Player(s) where a recorded transaction with AngularJS fails:

  • Increase CPU and RAM resources on the WPM Player.
  • Change the numWorkerProcesses value to 1 in C:\Program Files (x86)\SolarWinds\Orion\SEUM\Player\SolarWinds.SEUM.Agent.Service.exe.config and restart the WPM Playback Player service to apply the new configuration. This limits simultaneous worker processes on the WPM Player so only one transaction plays at a time and frees resources so they can be used by AngularJS.

An alternative is to schedule transaction recordings assigned to the WPM Player so that only one AngularJS step occurs during scheduled playback time. Restart the WPM Playback Player service to apply the new configuration. This approach is not recommended because it requires a script created outside of WPM.

 

 

Last modified

Tags

Classifications

Public