For NeoLoad to function properly, a Java library from the Oracle Forms application server must be copied in NeoLoad. The library must be placed in the folder specified in the message.

	Note
	Once the library has been copied into NeoLoad, you must re-start NeoLoad (you don't need to re-start the machine itself) for the changes to take effect.

Check the following:

The changes are not retroactive, so you need to make further recording. It may require several recordings until you find a functioning regular expression and the recorded requests are correctly decoded.

Before starting a new recording, make sure you have closed all browser instances, especially if some are still open and connected to Oracle Forms applets. Such non-decoded requests captured during recording usually come from Oracle Forms applets open in other browser instances.

NeoLoad does support the WebUtil technology. If WebUtil is used to communicate with dll's, there may be a conflict between the browser that is automatically launched by NeoLoad for the recording and the loading of these dll's. The best way to solve this is to launch the browser manually as follows:

Oracle Forms requests that have not been decoded correctly cannot be played back; nor can they be repaired. See the other questions and answers in this section of the documentation and try to identify the problem you are experiencing.

	Note
	Once a problem has been solved, we recommend you delete the previous recordings that did not play back correctly.

The Oracle Forms applet can sometimes send requests that contain components that are invalid at the time of recording. The problem can be solved in two ways.

	Note
	The changes are not retroactive, so the previous recordings are not affected. Consequently, if you wish to replay the previous recordings, they will need to be cleaned up by carrying out the procedure for manually deleting invalid components.

The problem is in the virtual user design. This indicates that the virtual user was not in the same graphical state in the Oracle Forms applet in the 2nd iteration as it was in the 1st. At the start of each iteration of the loop, the virtual user must be in the same graphical state, to the nearest click.

The graphical state of an Oracle Forms applet is defined as a set of graphical components existing at any one time. This example shows a component created in a server response:

<DataMessage>
  <actionCode>CREATE</actionCode>
  <handlerId>8</handlerId>
  <handlerClassId>259</handlerClassId>
  <properties>
    <Property>
      <id>DRAWN_CANVASUSAGE</id>
      <type>BYTE</type>
      <value objectClass="byte">3</value>
    </Property>
  </properties>
</DataMessage>

<DataMessage>
  <actionCode>DESTROY</actionCode>
  <handlerId>8</handlerId>
  <properties/>
</DataMessage>

	Note
	It is possible for a handlerId value to be re-used by a completely different type of graphical component later in the recording. These numerical identifiers are uniquely assigned by the server to concurrently occurring components, but may be used by several different components whose life cycles are disjoint.

There are several types of ifError, of which the most common are:

The Oracle Forms module may be used in DEBUG mode, which writes even more data to the log files. It can be turned on for debugging a specific use case, but never in a real test runtime.

During recording, data is written to log files named plugins.log.xxxxx.

During runtime, data is written to log files named loadgenerator.log.xxxxx.

You may quickly access the NeoLoad directory containing the log files by clicking on Help > Open logs folder.

When the server responds with ifError:7/500, NeoLoad reproduces the Oracle Forms applet's behavior: by default, it makes a maximum of 5 attempts to send the request to the server and receive a valid response, with a 1000 milliseconds interval between attempts. NeoLoad's behavior may be modified by editing the controller.properties configuration file.

Check the following: