tty.xml to 8181. Then I
>> observed only port 8181 was in used.
>>
>> - Triet
>>
>> --
>> View this message in context:
>> http://karaf.922171.n3.nabble.com/Multiple-instances-of-Karaf-on-same-host-tp1997807p2840993.html
>> Sent from the Karaf - User mailing list archive at Nabble.com.
>
8181 was in used.
- Triet
--
View this message in context:
http://karaf.922171.n3.nabble.com/Multiple-instances-of-Karaf-on-same-host-tp1997807p2840993.html
Sent from the Karaf - User mailing list archive at Nabble.com.
hat by setting the default port in jetty.xml to 8181. Then I
> observed only port 8181 was in used.
>
> - Triet
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/Multiple-instances-of-Karaf-on-same-host-tp1997807p2840993.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
like
they listen on both ports.
I verified that by setting the default port in jetty.xml to 8181. Then I
observed only port 8181 was in used.
- Triet
--
View this message in context:
http://karaf.922171.n3.nabble.com/Multiple-instances-of-Karaf-on-same-host-tp1997807p2840993.html
Sent from the
OK - thanks.
I assumed that the default 8080 port wasn't in use but it was hard to know
for sure.
/Bengt
2010/12/1 Achim Nierbeck
> 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
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
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:
org.osgi.service.http.port=8181
org.ops4j.pax.web.config.file=${karaf.base}/etc/jetty.xml
It means that you can override the jetty port in the jetty.xml
c
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
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 men
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
10 matches
Mail list logo
