Load generator tool issue (Load Runner)

We are using the LoadRunner load generator tool, and it seems to be leaving sessions hanging in server manager. I do see this in the Server Manager Log for my OAS instance though:

An Error occurred during Logout Cleanup| UserId: LOADRUN,Environment: JDEHYPD812, Role: *ALL,Key: OWVirtualGroup java.lang.NullPointerExceptionjava.lang.NullPointerExceptionat com.jdedwards.runtime.virtual.OWVirtual.notifyLogout(Unknown Source)at com.jdedwards.runtime.virtual.OWVirtualGroup.notifyLogout(Unknown Source)at com.jdedwards.services.login.LogoutCleanupThread$CleanupThread$Notifier.run(Unknown Source)at com.jdedwards.base.util.ThreadPool$WorkerThread.run(Unknown Source)29 Jan 2010 08:45:26,385[SEVERE][MAFLETCONTAINER]ERROR: unable to get node by ID (57_.._573940) because it wasn't in the NodeDataSource individual node cache. 29 Jan 2010 08:45:26,604[SEVERE][MAFLETCONTAINER]ERROR: unable to get node by ID (24390384500000-MGHIDWMNSV-FHSJEQYYYY_57_573949) because it wasn't in the NodeDataSource individual node cache. 29 Jan 2010 08:45:26,901[SEVERE][MAFLETCONTAINER]ERROR: unable to get node by ID (24390390000003-MGHIDWMNSV-FHSJEQYYYY_24390384500000-MGHIDWMNSV-FHSJEQYYYY_573954) because it wasn't in the NodeDataSource individual node cache. 29 Jan 2010 08:47:22,897[SEVERE][MAFLETCONTAINER]ERROR: unable to get node by ID (57_.._573940) because it wasn't in the NodeDataSource individual node cache. 29 Jan 2010 08:47:23,131[SEVERE][MAFLETCONTAINER]ERROR: unable to get node by ID (24390384500000-MGHIDWMNSV-FHSJEQYYYY_57_573949) because it wasn't in the NodeDataSource individual node cache. 29 Jan 2010 08:47:23,381[SEVERE][MAFLETCONTAINER]ERROR: unable to get node by ID (24390390000003-MGHIDWMNSV-FHSJEQYYYY_24390384500000-MGHIDWMNSV-FHSJEQYYYY_573954) because it wasn't in the NodeDataSource individual node cache.

We ran a 35 user test for 1 hour and I ended up with 138 sessions showing in Server Manager and 250+ session showing on my OAS monitor.

Any ideas would certainly be appreciated.

The support site appears to be down (at least for me, server connection timeout)

Thanks in advance

E1 8.12, Tools 8.98.1.2, OAS 10.1.3.1, AS/400 ES

Hi,
Do you have the Logout process as part of your load runner transaction script. Are all the transactions in loadrunner successful ?

Joel,

We do have a logout as part of the script, we also added a 'close browser' at the start of the transaction, just in case.

Not all transactions are successfull and they account for the bulk of the problems, I also asked the Utopia consultant to add a contingent logout in case of script failure, no joy

Tom

Sounds like your LR consultant is using HTTP scripting, what version of loadrunner is this ? I have worked with click and script protocol of loadrunner and created separated transactions for every event. The click on the logout link was a separate transaction. If your using a different scripting protocol i'm not sure how it impacts the functionality in JDE

Hello,

We are experiencing this same issue. Did you ever find a solution?

Thanks!

Hi everyone,
I will try also to create scripts for Load Runner, but I got an error in the replay , the snapshots from record and replay are different, in my replay I got the follow "You have beed logged out of this application" anyone has one example of how create one script with Loadrunner? I really appreciated the help