Accessing Big Data Discovery (BDD) URL Fails With 'Failed to initialize Collections'

(Doc ID 2023545.1)

Last updated on APRIL 03, 2017

Applies to:

Oracle Big Data Discovery - Version 1.0.0.0.0 and later
Generic Linux

Symptoms

Accessing Big Data Discovery (BDD) URL Fails With 'Failed to initialize Collections'

For Example:

http://server.domain:7003/bdd/

The Weblogic Managed Server log has the following error:


2015-06-22 18:08:18,132 ERROR [CollectionsInitFilter] Failed to initialize Collections
com.liferay.portal.PortalException: Failed to check/create Collections for use in Catalog
        at com.endeca.portal.catalog.CatalogCollectionsUtil.provisionCollections(CatalogCollectionsUtil.java:232)
        at com.liferay.portal.events.StartupHelper.createCatalogCollections(StartupHelper.java:223)
        at com.liferay.portal.events.StartupHelperUtil.createCatalogCollections(StartupHelperUtil.java:73)
        at com.liferay.portal.servlet.filters.init.CollectionsInitFilter.processFilter(CollectionsInitFilter.java:58)
        at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:91)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
        at com.liferay.portal.kernel.servlet.BaseFilter.processFilter(BaseFilter.java:154)
        at com.liferay.portal.kernel.servlet.BaseFilter.doFilter(BaseFilter.java:94)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:79)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3436)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3402)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
        at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
        at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
        at weblogic.servlet.internal.WebAppServletContext.doSecuredExecute(WebAppServletContext.java:2285)
        at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2201)
        at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
        at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1572)
        at weblogic.servlet.provider.ContainerSupportProviderImpl$WlsRequestExecutor.run(ContainerSupportProviderImpl.java:255)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
Caused by: com.oracle.endeca.pdi.mdex.config.ConfigClientException: com.sun.xml.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: OES-000303: Error tunneling request to Dgraph node. caused by: OES-000302: There is no Dgraph node available. Please check the Dgraph status. Please see the server log to find more detail regarding exact cause of the failure.
        at com.oracle.endeca.pdi.mdex.config.ConfigClientJaxws.getConfigElements(ConfigClientJaxws.java:163)
        at com.oracle.endeca.pdi.mdex.config.ConfigClientJaxws.createCollection(ConfigClientJaxws.java:91)
        at com.endeca.portal.catalog.CatalogCollectionsUtil.createProjectsCollection(CatalogCollectionsUtil.java:306)
        at com.endeca.portal.catalog.CatalogCollectionsUtil.provisionCollections(CatalogCollectionsUtil.java:224)
        ... 20 more
Caused by: com.sun.xml.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: OES-000303: Error tunneling request to Dgraph node. caused by: OES-000302: There is no Dgraph node available. Please check the Dgraph status. Please see the server log to find more detail regarding exact cause of the failure.




Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms