[
https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated GERONIMO-3481:
-----------------------------------
Attachment: GERONIMO-3481-2.patch
After a lot of help from David Blevins we seem to have figured out which parts
of the openejb deployer can be run without the container actually running.
I've modified EjbModuleBuilder to construct a ConfigurationFactory for each app
it deploys. I can deploy the mejb config with it as a car (without vamsi's
change). I still need to find all the appropriate resource adapters and
register their containerInfos, but I believe all the non-mdb ejb ContainerInfo
should be working with this patch.
This patch includes the MEJB patches from GERONIMO-3456 for your convenience in
testing. It also requires a slight change to openejb which I will attach as a
separate patch.
> 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-2.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.
