[GERONIMO-3481] Offline deployer throws BIND Exception when port 1099 is in use

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.1, 2.0.x, 2.1
• Fix Version/s: 2.0.2, 2.1
• Component/s: deployment
• Security Level: public (Regular issues)

Environment

G 2.0.1 - Running multiple instances

• Assignee: Vamsavardhana Reddy
• Reporter: Vamsavardhana Reddy
• Created: 20/Sep/07 05:30
• Updated: 23/Oct/07 14:16
• Resolved: 27/Sep/07 16:17

Description

Offline deployer throws Bind Exception when port 1099 is in use. Here is a scenario steps in which the problem is experienced.

1. Extract G-2.0.1-Tomcat distro to C:\
2. Create a dir "myserver" under C:\geronimo-j2ee-tomcat-2.0.1 and copy C:\geronimo-j2ee-tomcat-2.0.1\var to C:\geronimo-j2ee-tomcat-2.0.1\myserver\var (all sub-directories).
3. Edit C:\geronimo-j2ee-tomcat-2.0.1\myserver\var\config-substitutions.properties to set PortOffset=10.
4. Open a command window and start Geronimo. Since org.apache.geronimo.server.name is not set, this will start the default server instance.
5. Open a second command window, set GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=myserver. This will be command window to run the second server instance with name "myserver"
6. Run deploy.bat --offline list-modules.

At step 6, I am getting a BIND Exception since port 1099 is in use (by the default server instance) and the offline deployer is attempting to start rmi naming on port 1099. Since, this deploy command is run against second server instance, I would expect that it uses the configuration properties of "myserver" in which case it should use port 1109 to start rmi-naming if at all there is a need. When port 1099 is not in use, the offline deployer works as expected by updating proper config.xml file when a configuration is deployed/undeployed.

Issue Links

• is related to: GERONIMO-3546 sharedlib config should not start rmi-naming when used with offline deployer