brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From neykov <>
Subject [GitHub] brooklyn-server pull request: [OSGI] & CAMP pl...
Date Wed, 09 Mar 2016 16:46:00 GMT
GitHub user neykov opened a pull request:

    [OSGI] & CAMP platform init

    Also share the code with classic launcher.
    Getting an exception in the logs, which is coming from the `cxf-async-client` jar, used
by winrm. Seems like a bundle init ordering issue. Can be ignored for the time being, the
service being registered there is not used.
    2016-03-09 18:41:49,298 | ERROR | ort.http.async]) | configadmin                     
| 3 - org.apache.felix.configadmin - 1.8.8 | [, id=146,
bundle=84/mvn:org.apache.cxf/cxf-rt-transports-http-hc/3.1.4]: Unexpected problem updating
configuration org.apache.cxf.transport.http.async
    	at org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitFactory.addListener([84:org.apache.cxf.cxf-rt-transports-http-hc:3.1.4]
    	at org.apache.cxf.transport.http.asyncclient.AsyncHTTPConduitFactory.<init>([84:org.apache.cxf.cxf-rt-transports-http-hc:3.1.4]
    	at org.apache.cxf.transport.http.asyncclient.Activator$ConduitConfigurer.updated([84:org.apache.cxf.cxf-rt-transports-http-hc:3.1.4]

You can merge this pull request into a Git repository by running:

    $ git pull osgi/

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #52
commit e6b3ad900228d206f671f6e8b0350e95441e8ed1
Author: Svetoslav Neykov <>
Date:   2016-03-08T09:56:10Z

    [BROOKLYN-183] Load on OSGi init

commit ec3cc790a13363f07108725f1d810e9a244f35d5
Author: Svetoslav Neykov <>
Date:   2016-03-08T10:06:01Z

    [BROOKLYN-183] Reuse classic init code, loading CAMP platform


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message