Hi Dmitri, As I dug further into this, I discovered that two different versions of java were being used depending on how the app was started. Once we cleared that up, everything is working now.
Regards, Lisa JM Waugh Test Engineer CIO Software & Development Experience 1 704 907 7008 Mobile 1 720 342 5373 Office [email protected] IBM From: Dmitri T <[email protected]> Date: Tuesday, June 7, 2022 at 3:02 AM To: [email protected] <[email protected]> Subject: [EXTERNAL] Re: JMX works from UI but fails from CLI on Windows 10 I think the main problem is Received fatal alert: protocol_version and it indicates that JMeter is trying to use the TLS <https://developer.mozilla.org/en-US/docs/Web/Security/Transport_Layer_Security >(or maybe even obsolete SSL <https://developer.mozilla.org/en-US/docs/Glossary/SSL >) protocol which is not supported by the system under test (or vice versa) There should not be any differences between GUI and command-line modes of execution if you have 1 user, use the same JMeter and the same JDK. In case of higher loads non-GUI tests conduct much higher load than GUI ones (if there are no artificial slowing down factors like Timers <https://jmeter.apache.org/usermanual/component_reference.html#timers >) If you cannot figure out what's wrong yourself we'll need 2 jmeter.log files: one for GUI execution and one for non-GUI. In order to identify and fix the protocol issue you will need to add the next lines to /system.properties/ file (lives in "bin" folder of your JMeter installation) *javax.net.debug=all* and again attach 2 files from the STDOUT <https://en.wikipedia.org/wiki/Standard_streams#Standard_output_(stdout) >(JMeter console) More information: * Debugging SSL/TLS Connections <https://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/ReadDebug.html > * Apache JMeter Properties Customization Guide <https://www.blazemeter.com/blog/apache-jmeter-properties-customization > * javax.net.ssl.SSLException: Received fatal alert: protocol_version received when connecting to external applications <https://support.cloudbees.com/hc/en-us/articles/360028518251-javax-net-ssl-SSLException-Received-fatal-alert-protocol-version-received-when-connecting-to-external-applications > On 6/6/2022 10:11 PM, Lisa Waugh wrote: > > Hi, > > I have a JMX that work successfully from the JMeter UI but when I try > to run it with this command from the CLI all samplers fail > > timeStamp,elapsed,label,responseCode,responseMessage,threadName,dataType,success,failureMessage,bytes,sentBytes,grpThreads,allThreads,URL,Latency,IdleTime,Connect > > 1654544531892,2023,GET M2M /ngp/api/v1/assets,Non HTTP response code: > java.net.SocketException,Non HTTP response message: Connection > reset,Assets > 1-1,text,false,,3756,0,1,1,https://ngp-service-ui-dev.dal1a.ciocloud.nonprod.intranet.ibm.com/auth/m2m,0,0,1964 > > 1654544533916,0,GET M2M /ngp/api/v1/assets-0,200,OK,Assets > 1-1,text,true,,1171,0,1,1,null,0,0,0 > > 1654544533918,303,GET ALL /ngp/api/v1/assets,Non HTTP response code: > java.net.SocketException,Non HTTP response message: Connection > reset,Assets > 1-1,text,false,,2585,0,1,1,https://ngp-service-asset-dev.dal1a.ciocloud.nonprod.intranet.ibm.com/ngp/api/v1/assets,0,0,302 > > 1654544534222,151,POST /ngp/api/v1/assets,Non HTTP response code: > java.net.SocketException,Non HTTP response message: Connection > reset,Assets > 1-1,text,false,,4275,0,1,1,https://ngp-service-asset-dev.dal1a.ciocloud.nonprod.intranet.ibm.com/ngp/api/v1/assets/,0,0,146 > > 1654544534373,0,POST /ngp/api/v1/assets-0,200,OK,Assets > 1-1,text,true,,1690,0,1,1,null,0,0,0 > > 1654544534374,144,PUT /ngp/api/v1/assets/byid/,Non HTTP response code: > javax.net.ssl.SSLException,Non HTTP response message: Received fatal > alert: protocol_version,Assets > 1-1,text,false,,4161,0,1,1,https://ngp-service-asset-dev.dal1a.ciocloud.nonprod.intranet.ibm.com/ngp/api/v1/assets/byid/NotFound,0,0,142 > > 1654544534518,0,PUT /ngp/api/v1/assets/byid/-0,200,OK,Assets > 1-1,text,true,,1679,0,1,1,null,0,0,0 > > 1654544534519,152,PUT /ngp/api/v1/assets/byname/,Non HTTP response > code: java.net.SocketException,Non HTTP response message: Connection > reset,Assets > 1-1,text,false,,2585,0,1,1,https://ngp-service-asset-dev.dal1a.ciocloud.nonprod.intranet.ibm.com/ngp/api/v1/assets/byid/NotFound,0,0,151 > > 1654544534672,164,DEL ,Non HTTP response code: > javax.net.ssl.SSLException,Non HTTP response message: Received fatal > alert: protocol_version,Assets > 1-1,text,false,,2482,0,1,1,https://ngp-service-asset-dev.dal1a.ciocloud.nonprod.intranet.ibm.com/ngp/api/v1/assets/byid/1,0,0,163 > > This is the command used to run the jmx from the cli > > C:\IBM\apache-jmeter-5.4.3\apache-jmeter-5.4.3\bin\jmeter.bat -n -t > NextGen_asset.jmx -l NextGen_asset.jtl -LDEBUG > > And I’ll attach the jmeter.log also. > > Why on earth would it behave differently from the UI vs the command line? > > Regards, > > *Lisa JM Waugh* > > Test Engineer > > CIO Software & Development Experience > > 1 704 907 7008 Mobile > > 1 720 342 5373 Office > > [email protected] > > IBM > > > --------------------------------------------------------------------- > To unsubscribe, e-mail:[email protected] > For additional commands, e-mail:[email protected]
