hey deepak Currently Jmeter starts up, i have not recored and run my test on the same .bat (latest edited) file. i will work on Monday.
So now as you said QTP defines this _JAVA_OPTIONS variable and will it cause any prob for me while simulating load or running and recording of the script, because i have not work on it yet. >From your point of view(which is fine), should i carry on with latest edited jmeter.bat file ? And what about that thing create new .BAT file which Sebb told me to do so and i have already posted my comment on that too waiting for that feedback too Regards GP Deepak Shetty wrote: > > hi > which is fine, jmeter works without errors right? > _JAVA_OPTIONS is something the JRE looks for at startup and it looks like > QTP defines this environment variable... > > regards > deepak > > On Thu, Jan 28, 2010 at 9:21 PM, gpub <[email protected]> wrote: > >> >> hey Deepak >> >> edited as you said >> >> SET _JAVA_OPTIONS= >> >> %JM_START% %JM_LAUNCH% %JVM_ARGS% %ARGS% -jar >> "%JMETER_BIN%ApacheJMeter.jar" >> %JMETER_CMD_LINE_ARGS% >> >> Jmeter gets launched and cmd prompt appears with belwo message as: >> >> Picked up _JAVA_OPTIONS: >> >> >> guys my last message was not accepeted sent to the >> [email protected] mailing list 44 minutes ago >> >> Regards >> GP >> >> >> >> Deepak Shetty wrote: >> > >> > One Last try >> > edit JMeter.bat to add >> > SET _JAVA_OPTIONS= >> > just before the jmeter line. >> > >> > regards >> > deepak >> > >> > >> > >> > >> > On Thu, Jan 28, 2010 at 1:17 AM, gpub <[email protected]> wrote: >> > >> >> >> >> hi Deepak, >> >> yes launching Jmeter from .bat file only >> >> As you said i have edited .bat file >> >> >> >> echo %JM_START% >> >> echo %JM_LAUNCH% >> >> echo %JVM_ARGS% >> >> echo %ARGS% -jar >> >> echo %JMETER_BIN%ApacheJMeter.jar% >> >> echo %JMETER_CMD_LINE_ARGS% >> >> %JM_START% %JM_LAUNCH% %JVM_ARGS% %ARGS% -jar >> >> "%JMETER_BIN%ApacheJMeter.jar" >> >> %JMETER_CMD_LINE_ARGS% >> >> >> >> and Jmeter opens with result in cmd prompt as: >> >> >> >> ECHO is off. >> >> java.exe >> >> ECHO is off. >> >> -Xms256m -Xmx256m -XX:NewSize=128m -XX:MaxNewSize=128m >> >> -XX:SurvivorRatio=8 >> >> -XX:T >> >> argetSurvivorRatio=50 -XX:MaxTenuringThreshold=2 >> >> -XX:MaxLiveObjectEvacuationRati >> >> o=20 -Dsun.rmi.dgc.client.gcInterval=600000 >> >> -Dsun.rmi.dgc.server.gcInterval=6000 >> >> 00 -XX:PermSize=64m -XX:MaxPermSize=64m -jar >> >> ApacheJMeter.jar >> >> ECHO is off. >> >> Picked up _JAVA_OPTIONS: -Xrunjvmhook >> >> -Xbootclasspath/a:C:\PROGRA~1\COMMON~1\MER >> >> >> >> >> CUR~1\FUNCTI~1\Java\classes;C:\PROGRA~1\COMMON~1\MERCUR~1\FUNCTI~1\Java\classes\ >> >> jasmine.jar >> >> Loading Mercury Interactive QuickTest Professional Java Support >> (version >> >> 8.2.115 >> >> 1.0) (SUN 1.5.0_12) >> >> >> >> my view reads no info from the variable that are echoed. >> >> Jmeter's cmd prompt still gives message as in Bold letters >> >> >> >> Regards >> >> GP >> >> >> >> >> >> Deepak Shetty wrote: >> >> > >> >> > Just to confirm , you are launching jmeter by itself ...(not through >> >> QTP) >> >> > >> >> > On Wed, Jan 27, 2010 at 11:21 PM, Deepak Shetty <[email protected]> >> >> wrote: >> >> > >> >> >> Looks like Im mistaken and it isn't jvm args causing the >> >> problem.(because >> >> >> your echo didnt seem to return any values) >> >> >> The batch file you have to edit is jmeter.bat >> >> >> Towards the end there should be a line >> >> >> %JM_START% %JM_LAUNCH% %ARGS% %JVM_ARGS% -jar >> >> >> "%JMETER_BIN%ApacheJMeter.jar" %JMETER_CMD_LINE_ARGS% >> >> >> >> >> >> Before this line print out each of the above variables and see >> which >> >> one >> >> >> has the QTP specific parameters . Once you identify that you have >> to >> >> >> reset >> >> >> it (just before the above copied one) >> >> >> >> >> >> regards >> >> >> deepak >> >> >> >> >> >> >> >> >> >> >> >> On Wed, Jan 27, 2010 at 11:12 PM, gpub <[email protected]> >> wrote: >> >> >> >> >> >>> >> >> >>> hi >> >> >>> >> >> >>> Agreed that jmeter will work with 1.4 and 1.5. And i got your >> point >> >> >>> below >> >> >>> 1. edited the .bat file what you wrote below, same parameter has >> been >> >> >>> picked >> >> >>> up by jmeter (which you said is defined for QTP) >> >> >>> >> >> >>> Checked the Environment variable >> >> >>> name: _classload_hook; value=jvmhook >> >> >>> >> >> >>> name: _JAVA_OPTIONS >> >> >>> >> >> >>> >> >> >> value=Xbootclasspath/a:C:\PROGRA~1\COMMON~1\MERCUR~1\FUNCTI~1\Java\classes; >> >> >>> C:\PROGRA~1\COMMON~1\MERCUR~1\FUNCTI~1\Java\classes\jasmine.jar >> >> >>> >> >> >>> >> >> >>> 2 typed echo %JVM_ARGS% >> >> >>> C:\Documents and Settings\cc_gubhi>echo %JVM_ARGS% >> >> >>> %JVM_ARGS% >> >> >>> >> >> >>> as you said cannot pass the parameter that QTP has set and edited >> in >> >> as >> >> >>> JVM_ARGS=(empty) in .bat file >> >> >>> Can you please elaborate which line,where in and what exact to >> enter >> >> in >> >> >>> .bat >> >> >>> file ( exact wording ) >> >> >>> >> >> >>> uploaded the .bat file as .text, please do the necessary edits >> >> >>> http://old.nabble.com/file/p27351900/jmeter.text jmeter.text >> >> >>> >> >> >>> Regards >> >> >>> -- >> >> >>> GP >> >> >>> >> >> >>> >> >> >>> Deepak Shetty wrote: >> >> >>> > >> >> >>> > hi >> >> >>> > I do not know what you are asking me to comment on? >> >> >>> > >> >> >>> > JMeter will work with 1.4 and 1.5 without problems. However when >> >> you >> >> >>> are >> >> >>> > running on 1.5 you cannot pass the parameters that QTP has set >> (if >> >> you >> >> >>> > open >> >> >>> > any cmd window and type echo %JVM_ARGS% you should see some >> values >> >> >>> that >> >> >>> > QTP >> >> >>> > has setup). So you need to prevent JMeter from picking this up >> , >> >> one >> >> >>> of >> >> >>> > the >> >> >>> > ways is by setting JVM_ARGS= (empty) in jmeter.bat . This will >> not >> >> >>> affect >> >> >>> > QTP because it only applies to the cmd window on which Jmeter is >> >> >>> running. >> >> >>> > >> >> >>> > regards >> >> >>> > deepak >> >> >>> > >> >> >>> > On Wed, Jan 27, 2010 at 9:34 PM, gpub <[email protected]> >> >> wrote: >> >> >>> > >> >> >>> >> >> >> >>> >> hey Deepak thnx for the reply >> >> >>> >> Well i some im able to launch Jmeter reason was with two >> versions >> >> of >> >> >>> >> java >> >> >>> >> 1.4 and 1.5 on a system. And now jmeter is getting lauch with >> java >> >> >>> 1.5 >> >> >>> >> version(as i uninstalled version 1.4) and below message coming >> up >> >> on >> >> >>> >> command >> >> >>> >> prompt on QTP installed Machine: >> >> >>> >> >> >> >>> >> C:\Program Files\Java\jdk1.5.0_12\bin >> >> >>> >> Picked up _JAVA_OPTIONS: -Xrunjvmhook >> >> >>> >> -Xbootclasspath/a:C:\PROGRA~1\COMMON~1\MER >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> CUR~1\FUNCTI~1\Java\classes;C:\PROGRA~1\COMMON~1\MERCUR~1\FUNCTI~1\Java\classes\ >> >> >>> >> jasmine.jar >> >> >>> >> Loading Mercury Interactive QuickTest Professional Java Support >> >> >>> (version >> >> >>> >> 8.2.115 >> >> >>> >> 1.0) (SUN 1.5.0_12) >> >> >>> >> >> >> >>> >> Now i need more clarity from your side that shall i go ahead >> with >> >> >>> this >> >> >>> >> message coming in command prompt will not affect my jmeter runs >> or >> >> >>> need >> >> >>> >> to >> >> >>> >> set lines in .BAT file( if yes then which line). >> >> >>> >> >> >> >>> >> I am jst curious because on my 2 machine i am running jmeter >> with >> >> >>> java >> >> >>> >> 1.4 >> >> >>> >> version and on other 3 machine(having QTP) i am running with >> java >> >> >>> 1.5, >> >> >>> so >> >> >>> >> this is reason i want your comment so i can be confident to >> about >> >> the >> >> >>> >> message command prompt and i can go ahead with my runs. >> >> >>> >> >> >> >>> >> More over will this message above in command prompt cause me >> any >> >> prob >> >> >>> >> during >> >> >>> >> incremental load run. Please provide your valuable comments >> >> >>> >> >> >> >>> >> >> >> >>> >> Regards >> >> >>> >> GP >> >> >>> >> >> >> >>> >> >> >> >>> >> Deepak Shetty wrote: >> >> >>> >> > >> >> >>> >> > It looks like your QTP installation has put a value JVM_ARGS >> in >> >> >>> your >> >> >>> >> > environment variables in windows. These options are only >> valid >> >> for >> >> >>> java >> >> >>> >> > 1.4 >> >> >>> >> > (and you seem to be running jmeter with atleast java 1.5), >> and >> >> >>> shouldnt >> >> >>> >> > really be there for JMeter. >> >> >>> >> > Options >> >> >>> >> > a. Remove the JVM_ARGS variable from the environment, only >> add >> >> it >> >> >>> when >> >> >>> >> you >> >> >>> >> > need it >> >> >>> >> > OR >> >> >>> >> > b. modify jmeter.bat and add a line to it near the top saying >> >> >>> >> > set JVM_ARGS= >> >> >>> >> > (or whatever options you might want to pass) >> >> >>> >> > or call jmeter.bat having first reset JVM_ARGS to blank >> >> >>> >> > regards >> >> >>> >> > deepak >> >> >>> >> > >> >> >>> >> > >> >> >>> >> > On Wed, Jan 27, 2010 at 3:56 AM, gpub >> <[email protected]> >> >> >>> wrote: >> >> >>> >> > >> >> >>> >> >> >> >> >>> >> >> hi all, >> >> >>> >> >> >> >> >>> >> >> i am facing a prob while launching jmeter.bat file >> >> >>> >> >> >> >> >>> >> >> Issue is coming as below >> >> >>> >> >> >> >> >>> >> >> picked up _JAVA_OPTIONS: -Xrunjvmhook >> >> >>> >> >> -Xbootclasspath/a:C:\PROGRA~1\COMMON~1\MER >> >> >>> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >>> >> >> >> CUR~1\FUNCTI~1\Java\classes;C:\PROGRA~1\COMMON~1\MERCUR~1\FUNCTI~1\Java\classes\ >> >> >>> >> >> jasmine.jar >> >> >>> >> >> ERROR: JVMPI, an experimental interface, is no longer >> >> supported. >> >> >>> >> >> Please use the supported interface: the JVM Tool Interface >> (JVM >> >> >>> TI). >> >> >>> >> >> Error: could not load Mercury Interactive support. Please >> run >> >> the >> >> >>> >> setup >> >> >>> >> >> again. >> >> >>> >> >> If the problem persists please contact Mercury's >> Customer >> >> >>> >> support. >> >> >>> >> >> Error occurred during initialization of VM >> >> >>> >> >> -Xrun library failed to init: jvmhook >> >> >>> >> >> >> >> C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program >> >> >>> >> >> Files\Tortois >> >> >>> >> >> eSVN\bin;C:\Program Files\Windows Imaging\ >> >> >>> >> >> Picked up _JAVA_OPTIONS: -Xrunjvmhook >> >> >>> >> >> -Xbootclasspath/a:C:\PROGRA~1\COMMON~1\MER >> >> >>> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >>> >> >> >> CUR~1\FUNCTI~1\Java\classes;C:\PROGRA~1\COMMON~1\MERCUR~1\FUNCTI~1\Java\classes\ >> >> >>> >> >> jasmine.jar >> >> >>> >> >> ERROR: JVMPI, an experimental interface, is no longer >> >> supported. >> >> >>> >> >> Please use the supported interface: the JVM Tool Interface >> (JVM >> >> >>> TI). >> >> >>> >> >> Error: could not load Mercury Interactive support. Please >> run >> >> the >> >> >>> >> setup >> >> >>> >> >> again. >> >> >>> >> >> If the problem persists please contact Mercury's >> Customer >> >> >>> >> support. >> >> >>> >> >> Error occurred during initialization of VM >> >> >>> >> >> -Xrun library failed to init: jvmhook >> >> >>> >> >> errorlevel=1 >> >> >>> >> >> Press any key to continue . . . >> >> >>> >> >> >> >> >>> >> >> >> >> >>> >> >> please provide your valuable comments on the same, i am kind >> of >> >> >>> urgent >> >> >>> >> >> need >> >> >>> >> >> >> >> >>> >> >> Regards >> >> >>> >> >> GP >> >> >>> >> >> -- >> >> >>> >> >> View this message in context: >> >> >>> >> >> >> >> >>> >> >> >> >>> >> >> >> http://old.nabble.com/Jmeter-launching-prob%2C-urgent-help-needed-tp27337857p27337857.html >> >> >>> >> >> Sent from the JMeter - User mailing list archive at >> Nabble.com. >> >> >>> >> >> >> >> >>> >> >> >> >> >>> >> >> >> >> >>> >> --------------------------------------------------------------------- >> >> >>> >> >> To unsubscribe, e-mail: >> >> [email protected] >> >> >>> >> >> For additional commands, e-mail: >> >> >>> [email protected] >> >> >>> >> >> >> >> >>> >> >> >> >> >>> >> > >> >> >>> >> > >> >> >>> >> >> >> >>> >> -- >> >> >>> >> View this message in context: >> >> >>> >> >> >> >>> >> >> >> http://old.nabble.com/Jmeter-launching-prob%2C-urgent-help-needed-tp27337857p27351318.html >> >> >>> >> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> --------------------------------------------------------------------- >> >> >>> >> To unsubscribe, e-mail: >> [email protected] >> >> >>> >> For additional commands, e-mail: >> >> [email protected] >> >> >>> >> >> >> >>> >> >> >> >>> > >> >> >>> > >> >> >>> >> >> >>> -- >> >> >>> View this message in context: >> >> >>> >> >> >> http://old.nabble.com/Jmeter-launching-prob%2C-urgent-help-needed-tp27337857p27351900.html >> >> >>> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> >>> >> >> >>> >> >> >>> >> --------------------------------------------------------------------- >> >> >>> To unsubscribe, e-mail: [email protected] >> >> >>> For additional commands, e-mail: >> [email protected] >> >> >>> >> >> >>> >> >> >> >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://old.nabble.com/Jmeter-launching-prob%2C-urgent-help-needed-tp27337857p27353069.html >> >> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> >> For additional commands, e-mail: [email protected] >> >> >> >> >> > >> > >> >> -- >> View this message in context: >> http://old.nabble.com/Jmeter-launching-prob%2C-urgent-help-needed-tp27337857p27366764.html >> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > -- View this message in context: http://old.nabble.com/Jmeter-launching-prob%2C-urgent-help-needed-tp27337857p27369112.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
