How to debug problems when recording
JMeter Proxy does not record samples
If the browser is working OK, but the Proxy is not recording samples, then check that the browser really is using the JMeter Proxy.
One way to do this is to stop the JMeter Proxy. If the browser continues working, then it is clearly not using the Proxy.
Double-check the browser proxy settings. Clear the browser cache.
The JMeter proxy works by capturing the browser request, creating a sampler and adding it to the test plan, and then it runs the sampler. The response from the sampler is returned to the browser.
It’s very unlikely that the JMeter Proxy could return a response to the browser without the sampler appearing in the test plan. However, it’s worth checking the JMeter log file just in case.
Check ageInDays attributes in .xml configuration files.
To limit the size of generated LogGrabber zip files, by default LogGrabber should be capturing logs for a few days.
<server name=”Logs” logPath=”logs” includeSub=”true” isSiteScopeRelative=”true” ageInDays=”3″>
We can use full.loggrabber.conf.xml to collect more logs.
<server name=”Logs” logPath=”logs” includeSub=”true” isSiteScopeRelative=”true” ageInDays=”14″>
Or we can use Configuration Tool > Export configuration > [v] Include log files method as well.
SiteScope stores master.config information not just in master.config text file but also within __masterConfig persistency object.
When some changes are not reflected automatically, one may need edit both places to make them consistent when the service is stopped.
a. Edit <SiteScope installation>\groups\master.config using any text editor.
b. Edit persistency using <SiteScope installation>\bin\PersistencyViewer.bat
Filter by Type: com.mercury.sitescope.platform.configmanager.MasterConfig
Perform the following steps to launch SiteScope UI as a desktop application from SiteScope Local Client:
- Download the SiteScope-Client-2018.08.zip
- SiteScope version 2018.08.
- Extract the contents of the SiteScope-Client-2018.08.zip to a location of your choice.
- Navigate to the
dist folder and double-click
SiteScopeClient.bat. The SiteScope Local Client window opens.
- Enter the SiteScope URL in the format
http://<host name>:<port number>/SiteScope or
https://<host name>:<port number>/SiteScope for HTTPS connections. The SiteScope login screen opens.
- Enter your user credentials.The SiteScope UI opens.
To access secure connections (HTTPS) of SiteScope using the SiteScope local client, you must install the site security certificate into the Trusted Root Certification Authorities where local client is installed and running.
Install the security certificate on the server where thick client is installed
- Copy the security certificate from the SiteScope server.
- Double-click the
- On the Certificate dialog box, click Install Certificate to start the Certificate Import Wizard.
- On the Welcome page, click Next.
- On the Certificate Store page, select Place all certificates in the following store and click Browse.
- In the Select Certificate Store dialog box, select Show Physical Stores.
- Double-click Trusted Root Certification Authorities, select Local Computer, and then click OK.
On the Certificate Store page, click Next.
- On the summary page, review the details and click Finish. (note: the secure connections take a bit longer to load the GUI for the first time)
The following are some of the limitations of the SiteScope local client for this release:
- You cannot launch multiple instances of SiteScope using the local client.
- SiteScope with smart card authentication is not supported.
- Unified Console for the Chinese and Japanese locale is not supported.
- Report options such as Export, Select, and Email in the Monitor, Alert, and Server-centric reports do not work.
- Local client has to be closed and relaunched to continue to work with the SiteScope UI on:
- Loading a new license
- Restarting SiteScope from Infrastructure Preferences
- Help menu and options are not completely functional when launched from the local client.
||SiteScope versions 11.3x and later
||Windows 2008, 2012, 2016, 7, 10
Sitescope DB query monitor supports only direct SQL queries and not any PL/SQL kind of statements like variable declarations, set, define, conditional blocks etc.
select username from v$session where username like ‘u_name’
define u_name = ‘APPS’ select username from v$session where username like ‘u_name’; undefine u_name