jmeter压测https请求兼容问题

最新推荐文章于 2025-06-08 23:31:01 发布

小喜子898

最新推荐文章于 2025-06-08 23:31:01 发布

阅读量3.4k

点赞数 2

CC 4.0 BY-SA版权

分类专栏： jmeter

本文链接：https://blog.youkuaiyun.com/weixin_38250126/article/details/93713128

jmeter 专栏收录该内容

18 篇文章

订阅专栏

在使用JMeter进行APPserver接口压测时，遇到HTTPS协议握手失败的问题，表现为javax.net.ssl.SSLHandshakeException异常。通过更换JCE策略文件及升级JDK版本至1.8.0.191成功解决此问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

前提

jmeter版本：3.1

jdk：1.8.0.111(win64)

测试过程

1 在使用jmeter对APPserver接口进行压测，https协议握手失败，jmeter返回异常：

javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:553)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:412)
at ..............

解决方案

1 使用postman进行访问相同接口，请求和返回正常，怀疑jdk版本不一致导致编译问题；

2 根据网上说明jdk的缺陷，jdk里面有一个jce的包，安全性机制导致的访问https会报错，官网上有替代的jar包，换掉就好了

目录 %JAVA_HOME%\jre\lib\security里的local_policy.jar,US_export_policy.jar

JDK7 http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html

JDK8 http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html

替换后该问题还是尚未解决

3 卸载jdk，提升jdk版本为1.8.0.191 （下载地址：https://download.youkuaiyun.com/download/qq_39240270/10875745）该问题解决，请求和返回正常；

关于jdk1.8.0.111官网说明

core-libs/java.net
Disable Basic authentication for HTTPS tunneling
In some environments, certain authentication schemes may be undesirable when proxying HTTPS. Accordingly, the Basic authentication scheme has been deactivated, by default, in the Oracle Java Runtime, by adding Basic to the jdk.http.auth.tunneling.disabledSchemes networking property. Now, proxies requiring Basic authentication when setting up a tunnel for HTTPS will no longer succeed by default. If required, this authentication scheme can be reactivated by removing Basic from the jdk.http.auth.tunneling.disabledSchemes networking property, or by setting a system property of the same name to "" ( empty ) on the command line.

Additionally, the jdk.http.auth.tunneling.disabledSchemes and jdk.http.auth.proxying.disabledSchemes networking properties, and system properties of the same name, can be used to disable other authentication schemes that may be active when setting up a tunnel for HTTPS, or proxying plain HTTP, respectively.
JDK-8160838 (not public)