Notes and Limitations - Java Vuser protocols

This section describes notes and limitations for the Java protocols.

Tip: For general VuGen troubleshooting and limitations, see Troubleshooting and Limitations for VuGen.

Notes

  • 64-bit replay is not supported for Java over HTTP protocol. and for Java Record Replay or Java Vuser protocols when using web packages

  • 64-bit replay is not supported for Java Record Replay or Java Vuser protocols when using web packages.

  • Java Record Replay and Java over HTTP protocols: When recording on Internet Explorer 8 using the Java protocols, you must first close all instances of Internet Explorer before LoadRunner opens an Explorer instance for the record session.

  • VuGen provides a tool that enables you to convert a script created for Web, into Java. For more information, see Convert a Web - HTTP/HTML Vuser Script into a Java Vuser Script.

    Note: By default, Java 7 enables the Java Split Verifier. This prevents Java recording. VuGen uses the -XX:-UseSplitVerifier key while initializing the JVM during recording, to disable the verifier. This adaptation does not require any user intervention.

  • Although .NET-based and Java protocols support creating threads, we recommend that you do not use background threads in real load testing scenarios because:

    • Threads can degrade tests scalability.

    • Threads can affect performance measurements.

    • The utility functions' behavior is undetermined if called from any thread except the Vuser main thread which runs the vuser_init, Action, and vuser_end actions. This applies to all functions named lr*.

Back to top

Limitations

  • When you run a Java script, the replay status may be Script Not Run and some errors may appear in the mdrv.log file. However, due to Java internal architecture, these errors may not be included in the VuGen Output and Errors panes. This occurs when VuGen fails to initialize a Java Vuser, and JVM then terminates the replay process.

    Workaround: Look for errors directly in the mdrv.log file. If the entry in the log is due to a memory-related issue, try using different memory options for Java in the runtime settings.

Back to top

See also: