karaf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Achim Nierbeck <bcanh...@googlemail.com>
Subject Re: Multiple instances of Karaf on same host
Date Wed, 01 Dec 2010 21:45:57 GMT
Hi,

I didn't look into this to be 100% sure, but as far as I can see from
the behavior the jetty is started by the pax-web wrapper and after
pax receives the configuration by the configuration admin the jetty is
reconfigured. This should only be seen when either the container
is started or the pax-runner bundle is restarted, so this can be safely
ignored. :)

Regards, Achim


> Did you check that you don't have port defined in etc/jetty.xml ?
>
> For example, the Karaf http feature use a pax.web config like this:
>
> <config name="org.ops4j.pax.web">
>   org.osgi.service.http.port=8181
>   org.ops4j.pax.web.config.file=${karaf.base}/etc/jetty.xml
> </config>
>
> It means that you can override the jetty port in the jetty.xml
> configuration file.
>
> Regards
> JB
>
> On 12/01/2010 10:50 AM, Bengt Rodehav wrote:
>> Thanks for your reply Jean-Baptiste,
>>
>> I did think about "admin:create test" but I wasn't sure what ports it
>> will handle. Also, a specific installation (like ours) have a lot of
>> bundles that are not part of Karaf that needs to be taken care of.
>> That's why I wanted to be specific about what ports we use in production
>> and test respectively.
>>
>> Do you know why Jetty seems to configure port 8080 although I only
>> explicitly configure port 8181 (or 8180 in test)? I can't find where
>> this port is configured.
>>
>> /Bengt
>>
>> 2010/12/1 Jean-Baptiste Onofré <jb@nanthrax.net
>> <mailto:jb@nanthrax.net>>
>>
>>     Hi Bengt,
>>
>>     first, you can use the admin feature of Karaf.
>>
>>     To create a new Karaf instance, simply make:
>>
>>     admin:create test
>>
>>     It will create a new instance and manage the port number by itself.
>>     You can view the instances list (and the current state) using:
>>
>>     admin:list
>>
>>     Anyway, the files that you mentionned look good.
>>
>>     Regards
>>     JB
>>
>>
>>     On 12/01/2010 09:57 AM, Bengt Rodehav wrote:
>>
>>         I'm investigating whether we can install a test version of Karaf
>>         side-by-side (on the same host) as our production
>> installation. For
>>         different reasons this would be very useful for us.
>>
>>         One of the problems is to make sure that the two installations
>>         don't use
>>         the same ports. This is what I've found out this far. I list
>>         both the
>>         production and the test ports that I have chosen:
>>
>>         *etc/org.apache.karaf.management.cfg*
>>         - rmiRegistryPort=1099 (prod), 1100 (test)
>>
>>         *etc/org.ops4j.pax.web.cfg*
>>         - org.osgi.service.http.port=8181 (prod), 8180 (test)
>>         - org.osgi.service.http.port.secure=8443 (prod), 8444 (test)
>>
>>         *etc/org.apache.karaf.shell.cfg*
>>         - sshPort= 8101 (prod), 8102 (test)
>>
>>         Are the above all the ports I need to change in my test
>>         installation? I
>>         realize of course that this is not only a Karaf issue depending
>>         on what
>>         bundles I install but I'm interested to know whether I've missed
>>         anything that愀 part of Karaf that I need to reconfigure.
>>
>>
>>         I also seem to get a Jetty instance using the port 8080 although
>>         I do
>>         not configure that somewhere and I don't think it's really
>> used for
>>         anything. I get the following in my log:
>>
>>             2010-12-01 09:25:17,295 | DEBUG | Thread-8         |
>>             ServerControllerImpl             |
>>         ty.internal.ServerControllerImpl
>>                74 | Configuring server
>>             [ServerControllerImpl{state=UNCONFIGURED}] ->
>>             [ConfigurationImpl{http enabled=true,http port=8080,http
>> secure
>>             enabled=false,http secure port=8443,ssl
>>         keystore=C:\Documents and
>>             Settings\berodeha\.keystore,ssl keystoreType=null,session
>>             timeout=null,session url=null,session cookie=null,worker
>>             name=null,listening addresses=[Ljava.lang.String;@c9caf3}]
>>
>>
>>         If possible, I would like not to use that port at all or at
>>         least have
>>         the possibility to reconfigure it on my test installation.
>>
>>         /Bengt
>>
>>


Mime
View raw message