BAM Composer Is Not Loading, Showing Empty White Page (Doc ID 2495065.1)

Last updated on MAY 15, 2023

Applies to:

Symptoms

On : 12.2.1.3.0 version, BAM Dashboard

BAM Composer is not loading, showing empty white page

When I try to access the BAM composer, after login, the dashboard page is empty. This env used work fine, suddenly it broken. We trying to bring up for last couple of days. We observed following Error in log when we login Bam composer

ERROR
-----------------------

<Jan 8, 2019 12:47:38,817 PM EST> <Warning> <oracle.adfinternal.controller.state.AdfcContext> <ADFC-62008> <ADFc: This application is running in a cluster but High Availability mode is not enabled in adf-config.xml.>
<Jan 8, 2019 12:47:39,031 PM EST> <Warning> <org.apache.myfaces.trinidadinternal.style.xml.parse.StyleSheetDocument> <BEA-000000> <Circular dependency detected in style af|dvt-timeline>
<Jan 8, 2019 12:47:39,096 PM EST> <Warning> <oracle.adfinternal.view.faces.renderkit.rich.grid.CellGatherCallback> <ADF_FACES-30194> <Illegal width definition detected in panelGridLayout clientId="pt_psl5", gridRow id="gr2", gridCell id="gc9", width="100%" because columnSpan was not equal to 1 (columnSpan="2").>
java.lang.reflect.UndeclaredThrowableException
               at com.sun.proxy.$Proxy407.listProjects(Unknown Source)
               at oracle.beam.composer.navigator.DesignerNavigatorModel.listProjectNames(DesignerNavigatorModel.java:251)
               at oracle.beam.composer.navigator.DesignerNavigatorModel.getChosenNode(DesignerNavigatorModel.java:460)
               at oracle.beam.composer.navigator.DesignerNavigatorModel.getChooserActions(DesignerNavigatorModel.java:500)
...
Caused by: javax.naming.NameNotFoundException: While trying to lookup 'ConfigSession#oracle.beam.config.common.ConfigSession' didn't find subcontext 'ConfigSession#oracle'. Resolved ''; remaining name 'ConfigSession#oracle/beam/config/common/ConfigSession'
               at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1292)
               at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:349)
               at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:227)
               at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
               at weblogic.jndi.internal.ServerNamingNode.lookup(ServerNamingNode.java:527)
               at weblogic.jndi.internal.RootNamingNode.lookup(RootNamingNode.java:84)
               at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:307)
               at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:435)
               at javax.naming.InitialContext.lookup(InitialContext.java:417)
               at oracle.beam.common.client.BeamClient.getSession(BeamClient.java:805)
               at oracle.beam.common.client.BeamClient.getCurrentSession(BeamClient.java:612)
               at oracle.beam.common.client.BeamClient.invoke(BeamClient.java:945)
               ... 207 more
…
<Jan 8, 2019 12:49:07,442 PM EST> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed
java.lang.RuntimeException: javax.naming.NameNotFoundException: While trying to lookup 'OracleBeam#oracle.beam.common.alertsengine.timers.TimerAlertHelper' didn't find subcontext 'common'. Resolved 'OracleBeam#oracle.beam'; remaining name 'common/alertsengine/timers/TimerAlertHelper'.
java.lang.RuntimeException: javax.naming.NameNotFoundException: While trying to lookup 'OracleBeam#oracle.beam.common.alertsengine.timers.TimerAlertHelper' didn't find subcontext 'common'. Resolved 'OracleBeam#oracle.beam'; remaining name 'common/alertsengine/timers/TimerAlertHelper'

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.