geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vamsavardhana Reddy (JIRA)" <j...@apache.org>
Subject [jira] Updated: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
Date Fri, 21 Sep 2007 13:35:51 GMT

     [ https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vamsavardhana Reddy updated GERONIMO-3481:
------------------------------------------

    Attachment: GERONIMO-3481-weird.patch

GERONIMO-3481-weird.patch addressed this issue.  I can not explain how or why it works.  With
the patch, I have deployed a security realm and an ejb app using offline deployer without
hitting port any port conflicts.  Can someone explain how this is workiing?

Here is how I arrived at the patch:
1. I noticed that offline deployer is calling applyOverrides() on AttributeManager( based
on var/config/jsr88-configurer-config.xml) where as I will expect it to call the method on
ServerAttributeManager(based on var/config/config.xml)
2. With 1 in mind, I changed line 138 in KernelConfigurationManager to use configurationList
instead of attributeStore. This will not break the server as configurationList and attributeStore
are the same for it. But this resulted in test failures.
3. I reverted 2 and changed the online-deployer plan file so that ConfigurationManager->AttributeStore
uses ServerAttributeManager and ConfigurationManager->PersistentConfigurationList uses
AttributeManager. With this change, the deployer ran fine but did not update config.xml
4. I finally resorted to using ServerAttributeManager for both AttributeStore and PersistentConfigurationList
in online-deployer plan.

I thought it would compute all the configurations in config.xml as the configs to be started.
When I check in the debugger, it is computing only those five configs in jsr88-configurer-config.xml
as the configs to be started when the offline deployer is invoked.  MainConfigurationBootstrapper
is using the AttibuteManager from online-deployer config to get the persistent configurations
though AttributeManager is not connected with ConfigurationManager.

Note:  By offline deployer, I am referring to invoking deploy.bat with "--offline" option

> Offline deployer throws BIND Exception when port 1099 is in use
> ---------------------------------------------------------------
>
>                 Key: GERONIMO-3481
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3481
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 2.0.1, 2.0.x, 2.1
>         Environment: G 2.0.1 - Running multiple instances
>            Reporter: Vamsavardhana Reddy
>            Assignee: David Jencks
>             Fix For: 2.0.2, 2.0.x, 2.1
>
>         Attachments: GERONIMO-3481-1.patch, GERONIMO-3481-weird.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message