You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jakarta.apache.org by bu...@apache.org on 2010/09/01 15:09:11 UTC
DO NOT REPLY [Bug 49858] New: server mode should try binding to an
existing registry
https://issues.apache.org/bugzilla/show_bug.cgi?id=49858
Summary: server mode should try binding to an existing registry
Product: JMeter
Version: 2.4
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: enhancement
Priority: P2
Component: Main
AssignedTo: notifications@jakarta.apache.org
ReportedBy: toriverw@arrive.no
With the default jmeter.properties setting of server.rmi.create=true, JMeter in
server mode will try to start the registry. If the port (1099) is already in
use this will fail with
java.net.BindException: Address already in use: JVM_Bind
and JMeter exits.
I suggest that the behavior should change so that if the address is already in
use then it should fall back to assuming a registry is already running and try
to bind to it instead. This will be the same as the behavior JMeter server uses
when the JRE RMI registry (rmiregistry/rmid) is running separately and
jmeter.properties has server.rmi.create=false
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@jakarta.apache.org
For additional commands, e-mail: notifications-help@jakarta.apache.org
DO NOT REPLY [Bug 49858] server mode should try binding to an
existing registry
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49858
Sebb <se...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
--- Comment #1 from Sebb <se...@apache.org> 2010-09-02 18:40:03 EDT ---
It seems that JMeter 2.4 already behaves like this.
The log shows:
WARN - jmeter.engine.RemoteJMeterEngineImpl: Problem creating registry:
java.rmi.server.ExportException: Port already in use: 1099; nested exception
is:
java.net.BindException: Address already in use: JVM_Bind
INFO - jmeter.engine.RemoteJMeterEngineImpl: Bound to registry on port 1099
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@jakarta.apache.org
For additional commands, e-mail: notifications-help@jakarta.apache.org
DO NOT REPLY [Bug 49858] server mode should try binding to an
existing registry
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49858
--- Comment #2 from Tor I. Wilhelmsen <to...@arrive.no> 2010-09-03 03:00:52 EDT ---
Strange; I guess Windows instead had assigned the port to some other socket
when I tried and got the failure, while I assumed it was a different Java
process that had fired up the RMI registry.
I have resolved it locally (hopefully) by adding 1099/tcp to the etc/services
file.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@jakarta.apache.org
For additional commands, e-mail: notifications-help@jakarta.apache.org