We are currently testing the Oracle E-Business Suite using Silk Performer v7.4. We have created test scripts using Oracle Apps 11i protocol. A strange behavior we observed is that when executing a load test using agents of the MS Windows XP Pro SP2 OS, we do not observe any problems whereas when we run the same test scripts using MS Windows 2000 Server boxes as agents, we get 'Handler not found', and other 'Java Native errors'. The hotfix patch level of the Silk Performer installations on the both the boxes have been verified to be at the same level.
In addition to this another strange but repeated error that we observe during test runs, irrespective of the agent we use is "OraFormsJavaContainerAction Native: 1002 -Java Exception, Native Error 0: java.util.ConcurrentModificationException". This error occurs only during test runs and not during true log replays. We have not been able to trace this error to application related issues or any wrong input data that we might be giving to the test scripts. Currently we are clueless as to why this error occurs. segue's support site also does not seem to have this problem logged.
Any answers to both these problems is highly appreciated.
hmmmm, interesting.... One possible explanation is that W2K Server, multi-threading Os and might not have the configuration you need. True log replays only one VUser. Do you have the latest JSE or JVM installed on the Windows2000 Server machines? I would look at how the ODBC connection is set up. Also look at how SilkPerformer is configured as you might need to revisit the java settings.
I found this.... not sure how relevant it is or will be though
Issue: An exception may be reported before closing an oracle forms session. This is due to some special Oraforms 10g communication.
Workaround: If such an error occurs insert the function OraFormsHandlePendingOnExit just before the function that closes a oracle forms session.
Issue: JDK 1.2 has some deprecated functions that are required by SilkPerformer's Oracle Forms Engine.
Workaround: Do not use JDK 1.2 when recording/replaying Oracle Forms Applications. It is recommended to use the latest version of JDK to achieve better performance and stability. The JDK needs to be configured in the profile settings of your SilkPerformer project.
Issue: Hooking into the main Oracle Forms Applet classes might cause the JInitiator to be unable loading additional jar files that rely on the main classes.
Workaround: When recording Oracle Forms 6i or Oracle Applications 11i define the following Java Runtime Options in the JInitiator Properties Dialog:
NoVerify will prevent these loading issues.
Additionally the default Virtual Memory Size of JInitiator 1.1.7.x is between 16 and 64 MB. The option -mx128m will increase the virtual memory size to 128MB. This additional memory is needed as there is some extra memory overhead caused by recording. If you run into a OutOfMemory error you can further increase this value!
Also try to modify the heartbeat on the profil.
Usually it is 120 ms, reduce it less than the server value (usually equal to 120ms)
So set it to 90ms...
sometimes, it has a good influence on the load test.