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] Commented: (GERONIMO-3481) Offline deployer throws BIND Exception when port 1099 is in use
Date Sat, 22 Sep 2007 16:17:50 GMT

    [ 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 <import>classes</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\n            <import>... @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\n            <import>... @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\n            <import>...
@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 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