Select JMeter's Java Sampler for a JVM SOCKS Route

Pair JVM SOCKS properties with JMeter's Java HTTP implementation and keep HTTP proxy fields from overriding that route.

Use this JDK SOCKS path only when the relevant HTTP samplers can use JMeter's Java implementation. Its supported HTTP methods are narrower than HttpClient4; a PATCH workload needs another supported arrangement.

For an existing SOCKS listener, launch:

jmeter -n -t plan.jmx \
  -DsocksProxyHost=127.0.0.1 \
  -DsocksProxyPort=1080

A compatible no-account endpoint from the SOCKS proxy list can replace the example for permitted public requests executed by these Java samplers. Select Java in each relevant HTTP Request sampler or its HTTP Request Defaults. A sampler's explicit selection can override that default.

Leave its HTTP proxy host/port fields empty for this route. Populating them creates an explicit HTTP proxy; otherwise Java uses URL.openConnection() and the JDK's selection. Check existing HTTP/HTTPS JVM proxy properties too, since protocol-specific proxies take priority over SOCKS.

-D sets JVM system properties. -J sets JMeter's own properties and is not an alternative spelling.

Confirm the path with a representative request on the engine executing it. This configuration does not establish SOCKS routing for every plugin, JDBC connection, remote engine or other sampler.

Tënë sô zo