Summary: | Allow server mode to optionally use a fixed rmi port | ||
---|---|---|---|
Product: | JMeter - Now in Github | Reporter: | mathieu <mathieu.marante> |
Component: | Main | Assignee: | JMeter issues mailing list <issues> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 2.3.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows Server 2003 |
Description
mathieu
2009-01-30 06:12:39 UTC
The additional RMI ports are not opened by JMeter, but by the Java RMI code. As far as I know, there's no way to control these. If you can control these ports, then please re-open with the details. Turns out it is possible to bind the remote object to a specific port. If the JMeter property "server.rmi.localport" is defined before starting the JMeter server, then it will be used as the local port. Fixes committed to SVN trunk: URL: http://svn.apache.org/viewvc?rev=747989&view=rev Log: Bug 46636 - rmi ports Remote server now uses port defined by the property server.rmi.localport if present Simplified Client / Server classes Show remote object connections on console This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/2196 |