Hi,
If you are working with LR 11.50 or 11.51 please review the following KM Error: "Notify: Could not reserve enough space for object heap" causes a LoadRunner Java Record/Replay protocol script to fail during replay
Kind regards,
Hi,
If you are working with LR 11.50 or 11.51 please review the following KM Error: "Notify: Could not reserve enough space for object heap" causes a LoadRunner Java Record/Replay protocol script to fail during replay
Kind regards,
Thanks for the fast answer, but the page You send to me can't be viewed with my account. It gives me a page - " You are not authorized to view this document " so I couldn't see the article.
tgfofp
HP has supplied us a fix for this and a memory violation issue in the same module. The fix is conatined in a new version of LrXml.dll dated 11-13-2013.
Hope this helps.
Thanks for the reply vmanolova
but i think i couldn't define my problem correctly.
i'm saying that:
1 - Create Script
2 - Run the script
3 - Script got failed due to errors
4 - now LR 11.5 does display the error in a "Output Pane" but when i go to the "Replay" section and select the "Test Results" then the results doesn't displayed there
kindly do refer to the both attachments
one is snapshot and another is steps to reach Test Result option
Hi ,
I have around around 130 transactions in my recording for siebel protocol.But after recording vugen is not generating the script and throwing the error that failed to generate the script.
But if i am recording the script with the less number of transaction then its fine.
Can anybody help me in knowing , why vugen is not able to generate the script for the large number of scripts ?
Hello!
Some questions: What size do you need? Do you get an error without the extra Vm parameters?
Regards
Thomas
Hello!
I've tried with any kind of parameters , but the problem still persists. I have tried with any combination of Xms and Xmx with different sizes( like 20m to 256m for Xms , and 256m to 512m for Xmx ) but the result was the same; withouth the VM parameters it gives me the same error. The only difference with the original post for 2009 is that I'm using Java 6.
tgfofp
Hello all.
I was wondering if anybody but us are having problems with Truclient scripts corrupting themselves seemingly spontaneously.
We use Loadrunner 11.52 Patch 1 on all computers involved. OS is Windows 7 or Windows 2008 R2.
The problem is as follows: We develop Firefox Truclient scripts as usual, save in the Truclient view and then close Firefox. However, it appears Firefox doesn't actually close: We cannot save the script in the "regular" Vugen view after having exited Firefox. Vugen says "A TruClient script is currently being developed" but Firefox is closed and the Windows Task Manager verifies that no Firefox instance is currently running.
When we try to reopen the script we only get a white Firefox window. The script appears to be broken, or perhaps just the Firefox profile? We haven't been able to make any headway to solve this problem, so if you have any tips, please let me know and we'll try it right away.
A lot of work is being wasted and having to report that the scripts that were working just an hour ago now are broken is not a good thing for any of us.
Hi,
Regarding the knowledge document, if you have an active SAID which is added to your account you should be able to view the knowledge documents. The SAID can be linked to your account from the following link
https://support.openview.hp.com/entitlement/contracts
Kind regards,
Hi,
Is it possible to send request1 and request2 sametime by same Vuser?
(It doesn't matter what the order would be at remote end server side, only thing is that they would be sent away sametime.)
Thanks.
Have a look at web_concurrent_start() / web_concurrent_end() and evaluate if it's good enough for you.
This fixed the problem. I put the flag in the boot.ini and it makes the required heap for the VM.
Thank You very much!
Best regards,
tgfofp
PS: I could't find how to change the subject as closed.
Hi,
I am happy that you managed to open the KM and that you found the information which helped you to solve the problem.
Kind regards,
Hi,
In the past such a problem appeared due to installation issues and it was solved after reinstalling LoadRunner.
I would suggest you to upgrade to the latest LR 11.52 patch 1 version or if you are working with BPM to LR 11.51.
Kind regards,
We have recently installed Diagnostics with LoadRunner into an Oracle EBS environment and are having an issue with configuring the database Collectors.
Summary of our current setup
- LoadRunner 11.52 with Diagnostics
- Commander server 9.2
- Mediator server
- Probes installed with JVM's in Unix application servers
- Collectors installed in Oracle database servers running on Unix
If the Unix session where collector.sh was executed is exited the associated process also terminates. We are unable to view database details in Diagnostics unless the process executed with collector.sh is active. The Oracle databases are hosted by a third party so it is difficult to have these sessions opened on a regular basis.
Is there a way to have collector.sh active without an active Unix session?
I added Rendezvous in script, upload in ALM, and Create Performance Test with this script.
In the Edit Test - View Rendezvous screen, I could see the Rendezvous added from the script, and is Enable.
Apply one Policy and save the test.
When I run the test in Test Lab, there is no Rendezvous in View Rendezvous, what's the reason? and the running users seem like without Rendezvous.
Hey Thanks Madan,
Actually it was wrong screenshot I placed by mistakenly.
I am putting the correct IP but the result are the same,
Means replay fails at else condition..
Please suggest.
Regards,
Akshay
Hi All,
Would you please let me know in case we do have any function/method to ignore errors that displays when executing any Web Custom Request? I don't want these errors to display as these we are currently creating some scripts to get some data if the error displayed!
Thanks,
Tareq Hadid
It is very difficult to understand without looking at the script. Please provide the script you are working with to understand the problem.