Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: pass (nike.apache.org: domain of gnodet@gmail.com designates
 209.85.220.209 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=XSlAO+sO4Rkx46/f6IcN7eZ6dit179orBVnVOxPM9rbWghERJ+B4uIfiMMA8UNLo2O
         w0LoV9oXUg9P6FH31EKC5X3kGjtsUf7cCoCB1vZOAmeFeXhF5xM/3E+nCZrj7YeQQNiZ
         rvAPCOwIkHvCi8f2eVw1Z+WYlfMRm73OB4k4A=
MIME-Version: 1.0
In-Reply-To: <cfdb37fb0909070333m5925a6gb26398ebe5dd4900@mail.gmail.com>
References: <cfdb37fb0909070333m5925a6gb26398ebe5dd4900@mail.gmail.com>
Date: Mon, 7 Sep 2009 13:21:59 +0200
Message-ID: <b23ecedc0909070421m47eee1a9n74e59c1a497c6ff4@mail.gmail.com>
Subject: Re: [Karaf] admin:create'd instance launched from the command line
From: Guillaume Nodet <gnodet@gmail.com>
To: dev@felix.apache.org
Content-Type: multipart/alternative; boundary=0022158df8f7eb7c270472fb0e50

--0022158df8f7eb7c270472fb0e50
Content-Type: text/plain; charset=ISO-8859-1

Right, currently, the sshd port for child instances is managed by the
commands, but RMI and HTTP or any other port aren't.
I think it can be done through the command line by connecting to the child
instance and updating the configurations for the config admin, but it's
really tedious and a better way need to be found.

I guess we'd need a generic mechanism to handle port conflicts, not sure
what's the best way yet.

Thoughts welcomed !

On Mon, Sep 7, 2009 at 12:33, Eoghan Glynn <eoglynn@gmail.com> wrote:

> Hi Folks,
>
> If I launch an admin:create'd instance via admin:start from the master
> karaf
> instance, all is hunky-dorey.
>
> However, if instead the child instance is run from the command line via the
> generated instances/<name> directory tree, then I'm see a port clash on the
> JMX RMI connector[1] if the master instance is still runing.
>
> So I guess the question is, should we automatically override the jmxrmi
> port
> for the admin:create'd instance? (presumably via the serviceUrl property
> picked up by OSGI-INF/blueprint/karaf-management.xml)
>
> Or should the JMX RMI connector be disabled for the child instance? (as the
> management tooling may be expecting port 1099 or nothing)
>
> We may have a similar issue with the default 8181 port for the HTTP
> service.
>
> Cheers,
> Eoghan
>
>
> [1]
> Exception in thread "JMX Connector Thread
> [service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi]"
> java.lang.RuntimeException: Could not start JMX connector server
>    at
>
> org.apache.felix.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:103)
> Caused by: java.io.IOException: Cannot bind to URL
> [rmi://localhost:1099/jmxrmi]: javax.naming.NameAlreadyBoundException:
> jmxrmi [Root exception is java.rmi.AlreadyBoundException: jmxrmi]
>    at
>
> javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:804)
>    at
>
> javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:417)
>    at
>
> org.apache.felix.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:101)
> Caused by: javax.naming.NameAlreadyBoundException: jmxrmi [Root exception
> is
> java.rmi.AlreadyBoundException: jmxrmi]
>    at
> com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:122)
>


-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

--0022158df8f7eb7c270472fb0e50--