Resolution:
When running a Tryscript against some applications it might take a long time to complete compared to the same steps which were recorded. Some applications (such as Oracle Forms) can use a large number of jar files for client side functionality.
When an application web page is first visited, the .jar files are usually cached locally so that they can be accessed more quickly for future use - a standard Web Browser does this automatically. This is why for instance, some web pages take a longer time to load when first accessed than on subsequent visits.
When recording this first-time visit via Silk Performer the recorder will record and script lines of BDL code for all these files which might already reside in cache on the hard disk. Although this is expected behavior, unless you want to simulate a first time user who will download the jar files every time they access the website, it's possible to simply comment out the lines of code for files which should already have been cached. In effect the Vuser will then become a revisiting user with respect to those files.
Sample script before -
--------------------------
WebUrl("http://Mywebpage/common.jar", 0.0);
Sample script after -
------------------------
// COMMENTED OUT WebUrl("http://Mywebpage/common.jar", 0.0);
NOTE: SilkPerformer does not execute jar files on replay so it is only whether they are downloaded or not that is of concern.