[ https://issues.apache.org/jira/browse/FELIX-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15741954#comment-15741954 ]
Benson Margulies commented on FELIX-5415: ----------------------------------------- No, you wind up with two services either way. The service derived from the config-admin port will 'win' and be listening in Jetty. I have left the job where I hit this, so I can't go try it out and report back any longer. > HTTP leaves extra service registrations when configured with config admin > ------------------------------------------------------------------------- > > Key: FELIX-5415 > URL: https://issues.apache.org/jira/browse/FELIX-5415 > Project: Felix > Issue Type: Bug > Components: HTTP Service > Affects Versions: http.jetty-3.4.0 > Reporter: Benson Margulies > > If you set org.osgi.service.http.port to a port with configuration admin, you > will end up with multiple registrations of the service. One is created for > the port number that is visible from framework properties, the second from > the configuration admin information. If those ports are different, only the > second will be actually listening in jetty. The evidence is visible from the > gogo inspect command. -- This message was sent by Atlassian JIRA (v6.3.4#6332)