https://bz.apache.org/bugzilla/show_bug.cgi?id=63990
Bug ID: 63990
Summary: SSL RMI Binding
Product: JMeter
Version: 5.2.1
Hardware: PC
OS: Linux
Status: NEW
Severity: regression
Priority: P2
Component: Main
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: JMETER_5.2
In AWS when using Elastic IP for public IP mapping, it's not possible to use
SSL RMI as setting java.rmi.server.hostname when using SSL RMI, it wants to
bind to the provided address. This doesn't happen on non SSL setup, which
allows remote jmeter master to manage EC2 based jmeter runners.
Seems to be caused in RMIServerSocketFactoryImpl by the createServerSocket
override which also provides localAddress.
Security wise, it seems to not matter, as binding to a local address and
reporting a remote one requires non standard manual configuration.
Log from binding when using SSL RMI:
Server failed to start: java.rmi.server.ExportException: Listen failed on port:
1099; nested exception is:
java.io.IOException: Could not bind /XXX.XXX.XXX.XXX using port 1099
An error occurred: Listen failed on port: 0; nested exception is:
java.io.IOException: Could not bind to /XXX.XXX.XXX.XXX using port 1099
With -Jserver.rmi.ssl.disable=true it works without a hitch, therefore marking
it as regression.
--
You are receiving this mail because:
You are the assignee for the bug.
