From user-return-46803-archive-asf-public=cust-asf.ponee.io@jmeter.apache.org Sat Jun 9 16:53:07 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 6E282180648 for ; Sat, 9 Jun 2018 16:53:06 +0200 (CEST) Received: (qmail 88415 invoked by uid 500); 9 Jun 2018 14:53:05 -0000 Mailing-List: contact user-help@jmeter.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "JMeter Users List" Delivered-To: mailing list user@jmeter.apache.org Received: (qmail 88403 invoked by uid 99); 9 Jun 2018 14:53:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 09 Jun 2018 14:53:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 94E93CAD5D for ; Sat, 9 Jun 2018 14:53:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1 X-Spam-Level: * X-Spam-Status: No, score=1 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id VLmq-UfTv-qh for ; Sat, 9 Jun 2018 14:53:03 +0000 (UTC) Received: from internetallee.de (internetallee.de [81.169.162.220]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 8885B5F3BA for ; Sat, 9 Jun 2018 14:53:02 +0000 (UTC) Received: from [192.168.178.91] (p54888714.dip0.t-ipconnect.de [84.136.135.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by internetallee.de (Postfix) with ESMTPSA id EC18BE23546 for ; Sat, 9 Jun 2018 16:53:00 +0200 (CEST) Subject: Re: JMeter 4.0 client won't start if Secure RMI is configured To: user@jmeter.apache.org References: <743c681fc94b40d9956e64e7b60ad086@PSEXCH2013-02.aeroinfo.com> From: Felix Schumacher Message-ID: <497be8a6-b135-7cb5-671a-85bd3a1ae70a@internetallee.de> Date: Sat, 9 Jun 2018 16:53:00 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <743c681fc94b40d9956e64e7b60ad086@PSEXCH2013-02.aeroinfo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Am 09.06.2018 um 02:00 schrieb Andrey Shevtsov: > Hi, > > I asked this question on StackOverflow but got no answers or even tips so sending this to the mailing list. > > I am trying to set up remote testing infrastructure with secure RMI using JMeter 4.0 (one client and one server) but the client won't start because of 'Address already in use (Bind failed)' error. > netstat shows that no process is listening on this port and from the log it seems that JMeter itself tries to listen on the port more than once (at least that's how I interpreted the log messages). > Everything works fine if I disable Secure RMI (server.rmi.ssl.disable=true) > Both the client and server use 4.0 r1823414 version. > > You can find details and the log here (SO post) - https://stackoverflow.com/questions/50752126/unable-to-start-jmeter-4-0-client-with-ssl-rmi > > Let me know if you want me to provide any details/settings. Do you start server and client on different machines? What OS and Java version are you using? To which address does your hostname (on client and server) resolve? On my machine (server) jmeter prints out the following messages to the console: ./jmeter-server -Djava.rmi.server.hostname=192.168.1.24 Created remote object: UnicastServerRef2 [liveRef: [endpoint:[192.168.1.24:34743,SSLRMIServerSocketFactory(host=/192.168.1.24, keyStoreLocation=rmi_keystore.jks, type=JKS, trustStoreLocation=rmi_keystore.jks, type=JKS, alias=rmi),SSLRMIClientSocketFactory(keyStoreLocation=rmi_keystore.jks, type=JKS, trustStoreLocation=rmi_keystore.jks, type=JKS, alias=rmi)](local),objID:[...]]] Starting the test on host 192.168.1.24 @ Sat Jun 09 16:41:26 CEST 2018 (1528555286422) Finished the test on host 192.168.1.24 @ Sat Jun 09 16:41:27 CEST 2018 (1528555287862) On the client (started with ./jmeter -Djava.rmi.server.hostname=192.168.178.91) I see: 2018-06-09 16:47:37,714 INFO o.a.j.e.DistributedRunner: Configuring remote engine: 192.168.1.24 2018-06-09 16:47:37,815 INFO o.a.j.e.DistributedRunner: Starting remote engines 2018-06-09 16:47:37,815 INFO o.a.j.e.DistributedRunner: Starting the test @ Sat Jun 09 16:47:37 CEST 2018 (1528555657815) 2018-06-09 16:47:37,815 INFO o.a.j.e.ClientJMeterEngine: running clientengine run method 2018-06-09 16:47:37,816 INFO o.a.j.r.RmiUtils: Resolving by name the value of System property 'java.rmi.server.hostname': 192.168.1.91 2018-06-09 16:47:37,816 INFO o.a.j.r.RmiUtils: Local IP address=192.168.1.91 2018-06-09 16:47:37,823 INFO o.a.j.r.SSLRMIServerSocketFactory: Created SSLSocket: [SSL: ServerSocket[addr=/192.168.1.91,localport=36955]] 2018-06-09 16:47:37,824 INFO o.a.j.r.RmiUtils: Resolving by name the value of System property 'java.rmi.server.hostname': 192.168.1.91 2018-06-09 16:47:37,824 INFO o.a.j.r.RmiUtils: Local IP address=192.168.1.91 2018-06-09 16:47:37,832 INFO o.a.j.r.SSLRMIServerSocketFactory: Created SSLSocket: [SSL: ServerSocket[addr=/192.168.1.91,localport=44645]] 2018-06-09 16:47:37,838 INFO o.a.j.r.RmiUtils: Resolving by name the value of System property 'java.rmi.server.hostname': 192.168.1.91 2018-06-09 16:47:37,839 INFO o.a.j.r.RmiUtils: Local IP address=192.168.1.91 2018-06-09 16:47:37,844 INFO o.a.j.r.SSLRMIServerSocketFactory: Created SSLSocket: [SSL: ServerSocket[addr=/192.168.1.91,localport=45343]] 2018-06-09 16:47:37,845 INFO o.a.j.s.BatchSampleSender: Using batching (client settings) for this run. Thresholds: num=100, time=60000 2018-06-09 16:47:37,845 INFO o.a.j.s.DataStrippingSampleSender: Using DataStrippingSampleSender for this run 2018-06-09 16:47:38,108 INFO o.a.j.e.ClientJMeterEngine: sent test to 192.168.1.24 basedir='.' 2018-06-09 16:47:38,108 INFO o.a.j.e.ClientJMeterEngine: Sending properties {} 2018-06-09 16:47:38,117 INFO o.a.j.e.ClientJMeterEngine: sent run command to 192.168.1.24 2018-06-09 16:47:38,117 INFO o.a.j.e.DistributedRunner: Remote engines have been started 2018-06-09 16:47:38,132 INFO o.a.j.g.u.JMeterMenuBar: setRunning(true, 192.168.1.24) 2018-06-09 16:47:38,773 INFO o.a.j.g.u.JMeterMenuBar: setRunning(false, 192.168.1.24) It seems that for my very simple test case there were opened three local ports for RMI. So maybe it would help to unset the "client.rmi.localport" setting in your setup? Regards,  Felix > > Thank you! > Andrey Shevtsov > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org > For additional commands, e-mail: user-help@jmeter.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org For additional commands, e-mail: user-help@jmeter.apache.org