[
https://issues.apache.org/jira/browse/DOSGI-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider resolved DOSGI-219.
---------------------------------------
Resolution: Fixed
Assignee: Christian Schneider
The upcoming 2.0 version should work fine in karaf but I recommend to use karaf
4.x.
> DOSGi Fails to Publish Service Under Apache Karaf 3.0.3
> -------------------------------------------------------
>
> Key: DOSGI-219
> URL: https://issues.apache.org/jira/browse/DOSGI-219
> Project: CXF Distributed OSGi
> Issue Type: Bug
> Affects Versions: 1.6.0, 1.7.0
> Environment: Linux / Fedora 21 / RHEL 6.x / Apache Karaf 3.0.3
> Reporter: Craig Niles
> Assignee: Christian Schneider
>
> Hard to tell if this is a problem with the Karaf configuration or a bug in
> CXF. When trying to evaluate CXF DOSGi using Karaf 3.0.3, I encountered a
> bug where the same port is registered twice in jetty for the SOAP interface
> on the remote-service hosting instance of Karaf. I had the same problem for
> both Karaf feature repository versions 1.7.0-SNAPSHOT and 1.6.0. I tried
> using DOSGi version 1.4.0 and the problem does not occur.
> Its easy to reproduce:
> 1. Download and extract karaf 3.0.3 from
> http://karaf.apache.org/index/community/download.html
> 2. In the extracted karaf directory, modify
> etc/org.apache.karaf.features.repos.cfg and change the cxf-dosgi version from
> latests to 1.6.0 (or leave as LATEST to use snapshot)
> 3. Start karaf with ./bin/karaf , and use feature:repo-add cxf-dosgi to add
> the cxf feature repo
> 4. Install cxf dosgi distributed discovery using the command
> feature:install cxf-dosgi-distributed-discovery
> 5. Install the sample CXF DOSGi Discovery demo service implementation and
> API per http://cxf.apache.org/dosgi-discovery-demo-page.html
> 6. Start the services
> 7. Check the log file data/log/karaf.log There will be some stack traces
> resulting from the failure to bind the random port selected
> 8. Using lsof -i:<port> you can verify that the port is already bound to the
> process id of the running karaf instance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
