[jira] Commented: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
[ https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530638 ] David Jencks commented on GERONIMO-3481: I didn't get a chance to try it but the -for-2.0.patch looks fine to me. Have you checked that the (2) hack is really necessary with (1)? The code in Configuration looked right to me for handling transitive deps but I might be missing something. 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-2a.patch, GERONIMO-3481-3.patch, GERONIMO-3481-for-2.0.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.
[jira] Commented: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
[ https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530679 ] Vamsavardhana Reddy commented on GERONIMO-3481: --- Thanks David. I have verified that (2) is NOT necessary with (1). 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-2a.patch, GERONIMO-3481-3.patch, GERONIMO-3481-for-2.0.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.
[jira] Commented: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
[ https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530145 ] Vamsavardhana Reddy commented on GERONIMO-3481: --- GERONIMO-3484 is resolved. But then axis2-deployer is starting openejb :(. 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-2a.patch, GERONIMO-3481-3.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.
[jira] Commented: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
[ https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529674 ] Vamsavardhana Reddy commented on GERONIMO-3481: --- I am unable to use importclasses/import in openejb-deployer\pom.xml on branches\2.0. Here is the build error. [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: unknown POM Location: C:\G\server\branches\2.0\configs\openejb-deployer\pom.xml Reason: Parse error reading POM. Reason: Unrecognised tag: 'import' (position: S TART_TAG seen .../type\r\nimport... @55:21) [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Parse error reading POM. Reaso n: Unrecognised tag: 'import' (position: START_TAG seen .../type\r\n import... @55:21) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.InvalidProjectModelException: Parse error re ading POM. Reason: Unrecognised tag: 'import' (position: START_TAG seen .../typ e\r\nimport... @55:21) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default MavenProjectBuilder.java:1423) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default MavenProjectBuilder.java:1380) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi leInternal(DefaultMavenProjectBuilder.java:477) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave nProjectBuilder.java:200) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:537) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:511) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:511) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364) ... 11 more Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: Unrecognise d tag: 'import' (position: START_TAG seen .../type\r\nimport... @55:21) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseDependency(MavenX pp3Reader.java:1277) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.parseModel(MavenXpp3Re ader.java:2339) at org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.j ava:4438) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(Default MavenProjectBuilder.java:1419) ... 19 more [INFO] [INFO] Total time: 13 seconds [INFO] Finished at: Sat Sep 22 21:42:20 IST 2007 [INFO] Final Memory: 41M/75M [INFO] 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-2a.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
[jira] Commented: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
[ https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529693 ] Anita Kulshreshtha commented on GERONIMO-3481: -- The deployer syntax is deploy.bat . --port=n IIRC, the deployer has 1099 hard coded, i.e. if the port is not specified it will use 1099. Since we use same server image for all instances, I thought this interpretation was OK. This is one way to tell the deployer which server instance to deploy to. Of course we could do more, e.g. infer from geronimo_opts and use the right server instance. 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-2a.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.
[jira] Commented: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
[ https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529732 ] Vamsavardhana Reddy commented on GERONIMO-3481: --- The --port is not the way to point the deployer to the server instance it should work with. The --port option is used only by the online deployer. When --offline is specified, --port and --host are ignored. In online mode there is no need to worry about the instance of the server we are deploying to as the deployer 'connects' to the server. The offline deployer uses org.apache.geronimo.server.name system property to figure the server instance. It can be set by using GERONIMO_OPTS environment variable. For example GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=myserver will make the offline deployer use config files from GERONIMO_HOME/myserver/var/config. The problem is that offline deployer is not applying attribute overrides from myserver/var/config/config.xml (which has the port in question overridden to 1109) but from myserver/var/config/jsr88-configurer-config.xml. 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-2a.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.
[jira] Commented: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
[ https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529322 ] Vamsavardhana Reddy commented on GERONIMO-3481: --- David, thanks for the patch. GERONIMO-3481-1.patch does not seem to remove the openejb-deployer's dependency on openejb config. 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 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.
[jira] Commented: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
[ https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529358 ] Vamsavardhana Reddy commented on GERONIMO-3481: --- Added the missing attributes substitutionsFile and substitutionPrefix in rev 578021. 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 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.
[jira] Commented: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
[ https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529472 ] Vamsavardhana Reddy commented on GERONIMO-3481: --- Oh well... after looking at the code, GERONIMO-3481-weird.patch does not seem to be weird. MainBootstrapper.loadPersistentConfigurations() is using AbstractNameQuery(PersistentConfigurationList.class.getName()) to get to config lists. In case of online-deployer, the query is returning AttributeManager but not ServerAttributeManager. It is not picking up PersistentConfigurationList from ConfigurationManager gbean (which may be another problem). 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.
[jira] Commented: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
[ https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529015 ] Vamsavardhana Reddy commented on GERONIMO-3481: --- I am seeing the following gbean in configs/online-deployer plan.xml !--Server attribute service-- gbean name=ServerAttributeManager class=org.apache.geronimo.system.configuration.SwitchableLocalAttributeManager reference name=ServerInfo nameServerInfo/name /reference attribute name=configFilevar/config/config.xml/attribute /gbean Should it have the following attributes too? attribute name=substitutionsFilevar/config/config-substitutions.properties/attribute attribute name=substitutionPrefixorg.apache.geronimo.config.substitution./attribute If these two attributes are not set, how will it do the substitutions for properties used in config.xml? 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 Fix For: 2.0.2, 2.0.x, 2.1 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.
[jira] Commented: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
[ https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529310 ] David Jencks commented on GERONIMO-3481: This is caused by openejb-deployer starting openejb which starts almost all of geronimo. The solution is to make openejb-deployer only require the classes, not the running gbeans, of the openejb module. After a bunch of discussion with David Blevins this may not be impossible to do :-). 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 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.
