Run time error “Server Error in ‘LoadTest’ Application.” when we click on test

Run time error “Server Error in ‘LoadTest’ Application.” is observed when we click on scenario both in My Performance Center and DesktoClient version 12.56 .

The full error message is:

Server Error in ‘/LoadTest’ Application.

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a “web.config” configuration file located in the root directory of the current web application. This <customErrors> tag should then have its “mode” attribute set to “Off”.

<!– Web.Config Configuration File –>

<configuration>
<system.web>
<customErrors mode=”Off”/>
</system.web>
</configuration>
image text
The test can be edited but in the summary tab the error message appears.

The issue is observed when analysis template and/or resource monitors which were deleted from the project are used it the problematic test.

To overcome the issue the missing analysis template and/or resource monitors should be removed from the test.

1. If the test is using a deleted analysis template the options are in the test to choose another analysis template or the default analysis template by following the steps below:

Click on a problematic test
Click on Edit test button
In test window select Advanced-> Analysis Template Options
In the Analysis Template Options select:
Use default Analysis Template
Click on OK
Save the test

2. If the test is using a deleted monitor the missing monitor need to be removed from to test or substituted it with an existing monitor.

To delete a Monitor please follow the steps below:

Click on Associated Monitors tab
Select the missing Monitor
Click on Remove Selected
To add an existing monitor

Click on Associated Monitors tab
Select “Add Monitor Profile” or “Add Monitor OFW”
Select the Monitor from Select Monitors part of the screen.

Advertisements

Probe is not showed up in Diagnostics Enterprise interface

Telnet from Diagnostics server to localhost:2612

–If fails, Check /etc/server.properties timemanager.time_source=

–If timemanager.time_source=ntp, check Diagnostics server can access the internet.

Telnet to port 2612 for the Mediator specified in the property “mediator.host.name” in probe’s /etc/dynamic.properties file from probe machine.

Try to open probe URL /profiler/metrics?xml=true from the Diagnostics server.

• Check for Firewalls.

• Check if there is a proxy specified or needed.

• Try changing /etc/dispatcher.properties force.1.2.event.channel=true

• Try starting probe with -Dhttp.nonProxyHosts=<fully qualified name of the Diagnostics server>

How to change capture class map setting manually in diagnostics probe

To disable capture class map open probe.properties file in <probe_install>/etc. Look for use.class.map=. When capture class map is enabled it is set to true and will look like use.class.map=true. If you want to disable it and put things back to their default state, change the entry to use.class.map=auto.

How to enable Cross VM on probes

Enable Corba cross-VM on both probes. In diagnostics 8.x we added cross-VM support for pure IIOP which covers RMI over IIOP as well.

Enable Corba Cross-VM by following the steps below on both the probes:

a) Disable RMI in the points file in auto_detect.points file ([RMI] active = false)

b) Enable the Corba points (there is a Corba section towards the end of the auto_detect.points file)

c) Read the documentation under [Corba cross-VM Documentation] section of the points file and follow ALL the steps listed there.

d) After doing all of the above, the "jvmEntries" should look something like below.

-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.mercury.opal.javaprobe.handler.corba.CorbaORBInitializer

and

<java-agent-install-dir>/lib/probeCorbaInterceptors.jar

No data is displayed for “IBM WebSphere” monitors in the Diagnostics tab

LoadRunner: 9.52 running on Windows 2003, HP Diagnostics: Version 8.0, WebSphere Commerce: 6.x on AIX.

Retrieving data for the "Stand Views" graphs in diagnostics is working fine, but nothing is displayed for the "IBM WebSphere" views.

Java 2 Security is NOT enabled. The HP Diagnostics Performance Monitoring Infrastructure (PMI) statistic sets are selected as Extended.

Checking the probe.log on the AIX machined shows the following WARN log:

2010-05-06 10:20:09,836 WARN com.mercury.diagnostics.capture.metrics [Metrics Collection] Error initializing com.mercury.diagnostics.capture.metrics.jmx.JMXCollector@ca1f548

java.lang.IllegalAccessError: com.mercury.diagnostics.capture.metrics.jmx.JMXCollector tried to access method com/mercury/diagnostics/capture/metrics/jmx/JMXCollector$AttributesAndDescriptors.add(Ljava/lang/String;Lcom/mercury/diagnostics/common/metrics/MetricDescriptor;)V

Invalid classpath configuration on the IBM Websphere – HP Diagnositcs boot loader on the AIX machine.

Check the Boot Classpath configuration in the WebSphere Admin Console and ensure it has all the correct entries.

In this case it should have read:

/opt/MercuryDiagnostics/JavaAgent/DiagnosticsAgent/classes/IBM/1.4.2__1:

/opt/MercuryDiagnostics/JavaAgent/DiagnosticsAgent/classes/boot

but it did not have the first entry (1.4.2__1)

How can a probe (Java Agent) be bound to a specific network interface (NIC)

If the Diagnostics Java Agent (probe) is installed on a server that has multiple network interfaces (NIC) and there is a requirement to ensure that all network communications between the probe and its Mediator server occurs via a specific NIC

To bind the Java Agent (probe) to a specific network interface, edit the probe configuration file:

<Diagnostics_probe_install>\etc\webserver.properties

and specify the host address the probe is to bind to using:

# Host address to bind to. Uncomment this and specify an IP address if

# the SUT has multiple interfaces, and only one should be responding to

# HTTP requests.

#jetty.listen.host = 0.0.0.0

Restart the probe to apply the new configuration.

Exception Signal 11 while starting Java probe with the WebSphere

Immediately upon starting the WebSphere application server with Diagnostics Probe, the JVM crashes. In the dump file from the crash, if "Exception Signal 11" is observed in WebSphere logs.

E.g.

JVMDG217: Dump Handler is Processing Signal 11 – Please Wait.

JVMDG303: JVM Requesting Java core file

JVMDG304: Java core file written to /opt/WebSphere/AppServer/javacore.20101129.161814.22608.txt

JVMDG215: Dump Handler has Processed Exception Signal 11.

"signal 11 received" is seen in java core dump logs too.

Process level CPU usage metrics are not supported in probe for Linux 1.4.2 core, and though the probe should detect this initially, in some cases this didn’t happen.

Comment out the following metrics in etc/metrics.config file and restart the application/probe again:

ProcessMetrics/processCpuUtil=ProcessCpuUtil|percent|Probe

ProcessMetrics/processCpuUtilAbs = ProcessCpuUtilAbs|percent|Probe