Known issues for Java over HTTP

This section describes notes, limitations, and troubleshooting for the Java over HTTP protocol.

Tip: For general VuGen troubleshooting and limitations, see Known issues for VuGen.


  • For supported JDK versions, see the JDK/JRE support matrix.
  • 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*.

  • Java over HTTP supports asymmetric Java object traffic. This means that object serialization traffic is recognized even when it is on only one side of the communication. This occurs when the request is serialization and the response is plain HTTP, or vice versa.

Known issues

  • Snapshots are not supported for Java over HTTP.
  • You cannot use the GWT DFE extension or other Java-compatible DFE extensions. This is a result of a limitation of VuGen’s mdrv process, which only allows you to instantiate a single JVM.

  • Lazy evaluating objects are not supported, for example hibernate in lazy mode.
  • If there are stateful serialization mechanisms on the application server, this can interfere with VuGen's deserialization and result in unserialized data and unexpected errors.
  • The Remote Application via LoadRunner Proxy > Display recording toolbar on client machine option, is not supported for the Java over HTTP protocol. For details, see Start Recording dialog box.

  • 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


Back to top

See also: