The NoClassDefFoundError for Java-RMI protocol. There are several possibilities that this error occur such as (a) incomplete configuration of the Java environment requirements (refer to "Working with RMI-Java"), (b) incomplete reference to the Java libraries (usually located in {loadrunner-installation}\classes and {loadrunner-installation}\classes\srv after the required copy of the application's Java classes are placed in them) and (c) incorrect -Xbootclasspath to inform VUgen to point to the Java libraries for recording.

The error message that is thrown upon when the bootclasspath was not specified in the recording options is shown below:

java.lang.NoClassDefFoundError: jhook/HookMetaData
at java.rmi.Naming.lookup(Naming.java)
at pie.engine.atp.ClientRMI.getRemoteModuleImpl(ClientRMI.java:256)
at pie.engine.atp.ClientATPRemoteEx.getRemoteModule(ClientATPRemoteEx.java:89)
at pie.engine.atp.ClientATPRemoteEx.getRemoteModule(ClientATPRemoteEx.java:64)
at pie.engine.atp.VirtualRemoteServer.setupPingRemote(VirtualRemoteServer.java:102)
at pie.engine.atp.VirtualRemoteServer.pingServer(VirtualRemoteServer.java:166)
at pie.engine.atp.CacheTimer$1.run(CacheTimer.java:47)
at java.util.TimerThread.mainLoop(Timer.java:432)
at java.util.TimerThread.run(Timer.java:382)

To resolve the error was straight forward, enter the following to (a) the additional startup command to the recording options or (b) add it to the command batch file that is launching the Java application:

-Xbootclasspath/p:"D:\Program Files\LoadRunner\classes;D:\Program Files\LoadRunner\classes\srv"