Windows JMeter clientからLinuxな JMeter Serverでremote testする時のtips

俺です。JMeter素人がバレる記事その2です。

Windowsに仕込んだJMeter clientでJMeter remoteを実行した時、以下のエラーメッセージが出たらWindows Firewallを殺すかJMeter ServerのportをpassするようにFindows firewallルールのin/outに含めると良いです。

Engine is busy - cannot create JMeter engine

2017-07-08 21:01:49,055 WARN o.a.j.e.RemoteJMeterEngineImpl: Engine is busy - cannot create JMeter engine
2017-07-08 21:02:16,507 ERROR o.a.j.s.RemoteListenerWrapper: testStarted(host) on XX.XX.XX.XX:1099
java.rmi.ConnectException: Connection refused to host: XX.XX.XX.XX:1099; nested exception is:
    java.net.ConnectException: Connection timed out (Connection timed out)
    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619) ~[?:1.8.0_131]
    at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216) ~[?:1.8.0_131]
    at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202) ~[?:1.8.0_131]
    at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:130) ~[?:1.8.0_131]
    at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:227) ~[?:1.8.0_131]
    at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:179) ~[?:1.8.0_131]
    at com.sun.proxy.$Proxy21.testStarted(Unknown Source) ~[?:?]
    at org.apache.jmeter.samplers.RemoteListenerWrapper.testStarted(RemoteListenerWrapper.java:79) [ApacheJMeter_core.jar:3.2 r1790748]
    at org.apache.jmeter.engine.StandardJMeterEngine.notifyTestListenersOfStart(StandardJMeterEngine.java:220) [ApacheJMeter_core.jar:3.2 r1790748]
    at org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngine.java:388) [ApacheJMeter_core.jar:3.2 r1790748]
    at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
Caused by: java.net.ConnectException: Connection timed out (Connection timed out)
    at java.net.PlainSocketImpl.socketConnect(Native Method) ~[?:1.8.0_131]
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[?:1.8.0_131]
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[?:1.8.0_131]
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[?:1.8.0_131]
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:1.8.0_131]
    at java.net.Socket.connect(Socket.java:589) ~[?:1.8.0_131]
    at java.net.Socket.connect(Socket.java:538) ~[?:1.8.0_131]
    at java.net.Socket.(Socket.java:434) ~[?:1.8.0_131]
    at java.net.Socket.(Socket.java:211) ~[?:1.8.0_131]
    at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40) ~[?:1.8.0_131]
    at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:148) ~[?:1.8.0_131]
    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613) ~[?:1.8.0_131]
    ... 10 more

良い負荷試験Lifeを!

元記事はこちら

「Windows JMeter clientからLinuxな JMeter Serverでremote testする時のtips」