Hi Niranjan,
Yes. I can access osgi console. Here is the output of carbon-jndi bundle.
It is in ACTIVE state.
*osgi> ss jndi*
"Framework is launched."
id State Bundle
71 ACTIVE org.wso2.carbon.jndi_1.0.0.SNAPSHOT
*osgi> b 71*
org.wso2.carbon.jndi_1.0.0.SNAPSHOT [71]
Id=71, Status=ACTIVE Data
Root=/home/indika/dev-zone/wso2/fork/product-mb/product/target/wso2mb-3.5.0-SNAPSHOT/osgi/profiles/default/configuration/org.eclipse.osgi/71/data
"Registered Services"
{javax.naming.spi.ObjectFactory}={osgi.jndi.url.scheme=java, service.id=84,
service.bundleid=71, service.scope=singleton}
{javax.naming.spi.ObjectFactory}={osgi.jndi.url.scheme=osgi, service.id=85,
service.bundleid=71, service.scope=bundle}
{javax.naming.spi.InitialContextFactory}={service.id=86,
service.bundleid=71, service.scope=singleton}
{org.osgi.service.jndi.JNDIContextManager}={service.id=87,
service.bundleid=71, service.scope=bundle}
No services in use.
Exported packages
org.osgi.service.jndi; version="1.0.0"[exported]
Imported packages
javax.naming; version="0.0.0" <org.eclipse.osgi_3.10.2.v20150203-1939
[0]>
javax.naming.directory; version="0.0.0"
<org.eclipse.osgi_3.10.2.v20150203-1939 [0]>
javax.naming.spi; version="0.0.0"
<org.eclipse.osgi_3.10.2.v20150203-1939 [0]>
org.osgi.framework; version="1.8.0"
<org.eclipse.osgi_3.10.2.v20150203-1939 [0]>
org.slf4j; version="1.7.13"
<org.ops4j.pax.logging.pax-logging-api_1.8.5 [2]>
No fragment bundles
No required bundles
On Tue, May 17, 2016 at 10:26 PM, Niranjan Karunanandham <[email protected]>
wrote:
> Hi Indika,
>
> Are you able to start the access the osgi console? If so, can you check if
> carbon-jndi bundle is active?
>
> Regards,
> Nira
>
> On Tue, May 17, 2016 at 5:17 PM, Indika Sampath <[email protected]> wrote:
>
>> I update kernel version to 5.1.0-alpha2 and made necessary changes in
>> pom.xml. Also clone carbon-datasources and carbon-jndi, locally build and
>> update pom.xml with 1.0.0-SNAPSHOT. I didn't get any issue at build time.
>> But below exception throws at the server start up. Appreciate your input.
>>
>> indika@indika-Latitude-E6540:~/dev-zone/wso2/fork/product-mb/product/target/wso2mb-3.5.0-SNAPSHOT/bin$
>> ./carbon.sh
>> JAVA_HOME environment variable is set to /opt/jdk1.8.0_40
>> CARBON_HOME environment variable is set to
>> /home/indika/dev-zone/wso2/fork/product-mb/product/target/wso2mb-3.5.0-SNAPSHOT
>> osgi> 17:05:32.326 [Timer-0] ERROR
>> org.wso2.carbon.datasource.core.internal.DataSourceListenerComponent -
>> Error occurred while initializing data sources
>> org.wso2.carbon.datasource.core.exception.DataSourceException: Error in
>> initializing system data sources: Error in initializing data sources at
>> '/home/indika/dev-zone/wso2/fork/product-mb/product/target/wso2mb-3.5.0-SNAPSHOT/conf/datasources/master-datasources.xml
>> - Need to specify class name in environment or system property, or as an
>> applet parameter, or in an application resource file:
>> java.naming.factory.initial
>> at
>> org.wso2.carbon.datasource.core.DataSourceManager.initDataSources(DataSourceManager.java:142)
>> ~[69:org.wso2.carbon.datasource.core:1.0.0.SNAPSHOT]
>> at
>> org.wso2.carbon.datasource.core.internal.DataSourceListenerComponent.onAllRequiredCapabilitiesAvailable(DataSourceListenerComponent.java:84)
>> [69:org.wso2.carbon.datasource.core:1.0.0.SNAPSHOT]
>> at
>> org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver.lambda$notifySatisfiableComponents$17(StartupOrderResolver.java:412)
>> [65:org.wso2.carbon.core:5.1.0.alpha2]
>> at
>> org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver$$Lambda$69/997783091.accept(Unknown
>> Source) [65:org.wso2.carbon.core:5.1.0.alpha2]
>> at java.util.ArrayList.forEach(ArrayList.java:1249) [?:?]
>> at
>> org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver.notifySatisfiableComponents(StartupOrderResolver.java:397)
>> [65:org.wso2.carbon.core:5.1.0.alpha2]
>> at
>> org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver.access$100(StartupOrderResolver.java:78)
>> [65:org.wso2.carbon.core:5.1.0.alpha2]
>> at
>> org.wso2.carbon.kernel.internal.startupresolver.StartupOrderResolver$1.run(StartupOrderResolver.java:217)
>> [65:org.wso2.carbon.core:5.1.0.alpha2]
>> at java.util.TimerThread.mainLoop(Timer.java:555) [?:?]
>> at java.util.TimerThread.run(Timer.java:505) [?:?]
>> Caused by: org.wso2.carbon.datasource.core.exception.DataSourceException:
>> Error in initializing data sources at
>> '/home/indika/dev-zone/wso2/fork/product-mb/product/target/wso2mb-3.5.0-SNAPSHOT/conf/datasources/master-datasources.xml
>> - Need to specify class name in environment or system property, or as an
>> applet parameter, or in an application resource file:
>> java.naming.factory.initial
>> at
>> org.wso2.carbon.datasource.core.DataSourceManager.initDataSource(DataSourceManager.java:169)
>> ~[?:?]
>> at
>> org.wso2.carbon.datasource.core.DataSourceManager.initDataSources(DataSourceManager.java:137)
>> ~[?:?]
>> ... 9 more
>> Caused by: javax.naming.NoInitialContextException: Need to specify class
>> name in environment or system property, or as an applet parameter, or in an
>> application resource file: java.naming.factory.initial
>> at
>> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
>> ~[?:?]
>> at
>> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
>> ~[?:?]
>> at
>> javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:350)
>> ~[?:?]
>> at javax.naming.InitialContext.lookup(InitialContext.java:417) ~[?:?]
>> at
>> org.wso2.carbon.datasource.core.DataSourceJndiManager.lookupJNDISubContext(DataSourceJndiManager.java:135)
>> ~[?:?]
>> at
>> org.wso2.carbon.datasource.core.DataSourceJndiManager.checkAndCreateJNDISubContexts(DataSourceJndiManager.java:115)
>> ~[?:?]
>> at
>> org.wso2.carbon.datasource.core.DataSourceJndiManager.getBindingContext(DataSourceJndiManager.java:95)
>> ~[?:?]
>> at
>> org.wso2.carbon.datasource.core.DataSourceJndiManager.register(DataSourceJndiManager.java:75)
>> ~[?:?]
>> at
>> org.wso2.carbon.datasource.core.DataSourceJndiManager.register(DataSourceJndiManager.java:50)
>> ~[?:?]
>> at
>> org.wso2.carbon.datasource.core.DataSourceManager.initDataSource(DataSourceManager.java:165)
>> ~[?:?]
>> at
>> org.wso2.carbon.datasource.core.DataSourceManager.initDataSources(DataSourceManager.java:137)
>> ~[?:?]
>> ... 9 more
>>
>>
>> On Fri, May 13, 2016 at 4:26 PM, Niranjan Karunanandham <
>> [email protected]> wrote:
>>
>>> Hi Hemika,
>>>
>>> The startup resolver changes compatible to kernel 5.1.0-alpha2 is
>>> available in the master branch (PR [1]) of carbon-datasources. The
>>> carbon-datasources 1.0.0-alpha depends on the older format.
>>>
>>> [1] - https://github.com/wso2/carbon-datasources/pull/14
>>>
>>> Regards,
>>> Nira
>>>
>>> On Fri, May 13, 2016 at 4:22 PM, Hemika Kodikara <[email protected]>
>>> wrote:
>>>
>>>> Thanks for the response. I have changed the kernel version to
>>>> 5.1.0-alpha2 as mentioned. The earlier error is not coming. But I am
>>>> getting the following error. Seems like its coming from carbon-datasources.
>>>> I checked this with m1 version and also alpha version for datasources.
>>>>
>>>> =========================
>>>> [2016-05-13 15:16:04,974] ERROR {org.wso2.carbon.core} - FrameworkEvent
>>>> ERROR - org.wso2.carbon.core
>>>> org.wso2.carbon.kernel.internal.startupresolver.StartOrderResolverException:
>>>> componentName value is missing in the services registered with the key
>>>> org.wso2.carbon.kernel.startupresolver.RequiredCapabilityListener,
>>>> implementation class name is
>>>> org.wso2.carbon.datasource.core.internal.DataSourceListenerComponent
>>>> at
>>>> org.wso2.carbon.kernel.internal.startupresolver.OSGiServiceCapabilityTracker$CapabilityServiceTrackerCustomizer.addingService(OSGiServiceCapabilityTracker.java:142)
>>>> at
>>>> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:941)
>>>> at
>>>> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:870)
>>>> at
>>>> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
>>>> at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
>>>> at
>>>> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:901)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:109)
>>>> at
>>>> org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:914)
>>>> at
>>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>> at
>>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:862)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:801)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:127)
>>>> at
>>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:225)
>>>> at
>>>> org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:464)
>>>> at
>>>> org.eclipse.equinox.internal.ds.InstanceProcess.registerService(InstanceProcess.java:536)
>>>> at
>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:213)
>>>> at
>>>> org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:473)
>>>> at
>>>> org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:217)
>>>> at
>>>> org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:816)
>>>> at
>>>> org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:783)
>>>> at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
>>>> at
>>>> org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)
>>>>
>>>> ==================
>>>>
>>>> Regards,
>>>> Hemika
>>>>
>>>>
>>>> Hemika Kodikara
>>>> Software Engineer
>>>> WSO2 Inc.
>>>> lean . enterprise . middleware
>>>> http://wso2.com
>>>>
>>>> Mobile : +94777688882
>>>>
>>>> On Fri, May 13, 2016 at 3:00 PM, Niranjan Karunanandham <
>>>> [email protected]> wrote:
>>>>
>>>>> Hi Hemika,
>>>>>
>>>>> There has been some changes to the Startup Resolver in the
>>>>> 5.1.0-alpha2 release. Therefore IMO it would be better if you can use
>>>>> 5.1.0-alpha2 and carbon-parent version 5.
>>>>>
>>>>> Regards,
>>>>> Nira
>>>>>
>>>>> On Fri, May 13, 2016 at 2:51 PM, Hemika Kodikara <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> I am getting this error when starting up the MB C5 pack. We are
>>>>>> working on the released 5.0.0 version of carbon-kernel. Any idea how this
>>>>>> error occurs and how to avoid it ?
>>>>>>
>>>>>> ================================
>>>>>>
>>>>>> [2016-05-13 14:43:28,491] ERROR
>>>>>> {org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator}
>>>>>> - Failed to initialize startup resolver. java.lang.RuntimeException:
>>>>>> capability-name value is missing in Provide-Capability header
>>>>>> at
>>>>>> org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator.getManifestElementAttribute(RequireCapabilityCoordinator.java:381)
>>>>>> at
>>>>>> org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator.lambda$processManifestHeaders$21(RequireCapabilityCoordinator.java:287)
>>>>>> at
>>>>>> org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator$$Lambda$36/
>>>>>> 2099832114.accept(Unknown Source)
>>>>>> at
>>>>>> java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374)
>>>>>> at
>>>>>> java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580)
>>>>>> at
>>>>>> org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator.processManifestHeaders(RequireCapabilityCoordinator.java:283)
>>>>>> at
>>>>>> org.wso2.carbon.kernel.internal.startupresolver.RequireCapabilityCoordinator.start(RequireCapabilityCoordinator.java:120)
>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>> at
>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>>>>> at
>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>>> at java.lang.reflect.Method.invoke(Method.java:497)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:235)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:473)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:217)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:816)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:783)
>>>>>> at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
>>>>>> at
>>>>>> org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:70)
>>>>>>
>>>>>> =============================
>>>>>>
>>>>>> Regards,
>>>>>> Hemika
>>>>>>
>>>>>> Hemika Kodikara
>>>>>> Software Engineer
>>>>>> WSO2 Inc.
>>>>>> lean . enterprise . middleware
>>>>>> http://wso2.com
>>>>>>
>>>>>> Mobile : +94777688882
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> *Niranjan Karunanandham*
>>>>> Senior Software Engineer - WSO2 Inc.
>>>>> WSO2 Inc.: http://www.wso2.com
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> *Niranjan Karunanandham*
>>> Senior Software Engineer - WSO2 Inc.
>>> WSO2 Inc.: http://www.wso2.com
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> [email protected]
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Indika Sampath
>> Senior Software Engineer
>> WSO2 Inc.
>> http://wso2.com
>>
>> Phone: +94 716 424 744
>> Blog: http://indikasampath.blogspot.com/
>>
>>
>
>
> --
>
> *Niranjan Karunanandham*
> Senior Software Engineer - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>
--
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com
Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
