Thanks Thusitha for the clarification. After adding necessary entries in [1] I was able to get rid of the WARN log. However, I came across another error related to the trigger-provider component. Reported a JIRA[2] for that.
[1] https://github.com/wso2/carbon-gateway-framework/blob/ma ster/gateway-core/components/org.wso2.carbon.gateway.core/pom.xml#L160 [2] https://wso2.org/jira/browse/CGF-7 Farasath Ahamed Software Engineer, WSO2 Inc.; http://wso2.com Mobile: +94777603866 Blog: blog.farazath.com Twitter: @farazath619 <https://twitter.com/farazath619> <http://wso2.com/signature> On Fri, Sep 23, 2016 at 5:39 PM, Thusitha Thilina Dayaratne < [email protected]> wrote: > Hi Farasath, > > AFAIK, this warning implies that there is an OSGi component with the name > *trigger-provider[1] *but that hasn't been mentioned in the > Carbon-Component header in the *org.wso2.carbon.gateway.core[2] *bundle. > To get rid of that warning that should be specified as a carbon-component > in the gateway.core bundle. > > I also noticed that the OSGi console is enabled by default without passing >> any command line args when starting the server? Is this the expected >> behaviour? > > Yes. From C5 onwards that is enable by default. > > [1] - https://github.com/wso2/carbon-gateway-framework/blob/ > master/gateway-core/components/org.wso2.carbon.gateway.core/src/main/java/ > org/wso2/carbon/gateway/core/flow/triggers/EndpointTriggerServiceComponen > t.java > [2] - https://github.com/wso2/carbon-gateway-framework/blob/ > master/gateway-core/components/org.wso2.carbon.gateway.core/pom.xml#L160 > > Thanks > Thusitha > > On Fri, Sep 23, 2016 at 5:08 PM, Farasath Ahamed <[email protected]> > wrote: > >> Hi All, >> >> I build the product-integration-server from source and started the server >> by running carbon.sh script. >> I noticed the below WARN log, >> >> osgi> [2016-09-23 17:01:24,002] * WARN >> {org.wso2.carbon.kernel.internal.startupresolver.StartupComponentManager} - >> Adding a RequiredCapabilityListener from >> bundle(org.wso2.carbon.gateway.core:1.0.0.SNAPSHOT), but specified startup >> component is not available, component-name: trigger-provider* >> [2016-09-23 17:01:24,007] INFO {org.wso2.carbon.gateway.core. >> service.GatewayServiceComponent} - Starting Gateway...! >> [2016-09-23 17:01:24,084] INFO {org.wso2.carbon.transport.htt >> p.netty.internal.NettyTransportServiceComponent} - All >> CarbonNettyServerInitializers are available >> [2016-09-23 17:01:24,104] INFO {org.wso2.carbon.transport.htt >> p.netty.listener.NettyListener} - Starting Netty Http Transport Listener >> [2016-09-23 17:01:24,190] INFO {org.wso2.carbon.transport.htt >> p.netty.listener.NettyListener} - Netty Listener starting on port 9090 >> [2016-09-23 17:01:24,193] INFO >> {org.wso2.carbon.kernel.internal.CarbonStartupHandler} >> - WSO2 Carbon started in 1.325 sec >> >> >> Can this warn log be ignored? >> I also noticed that the OSGi console is enabled by default without >> passing any command line args when starting the server? Is this the >> expected behaviour? >> >> >> Thanks, >> Farasath Ahamed >> Software Engineer, WSO2 Inc.; http://wso2.com >> Mobile: +94777603866 >> Blog: blog.farazath.com >> Twitter: @farazath619 <https://twitter.com/farazath619> >> <http://wso2.com/signature> >> >> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Thusitha Dayaratne > Software Engineer > WSO2 Inc. - lean . enterprise . middleware | wso2.com > > Mobile +94712756809 > Blog alokayasoya.blogspot.com > About http://about.me/thusithathilina > <http://wso2.com/signature> > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
