BAM 12c: The following error is constantly seen on BAM Composer 'an error had happened see the logs' and contact administrator.

(Doc ID 2383231.1)

Last updated on APRIL 12, 2018

Applies to:

Oracle BAM (Business Activity Monitoring) - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.1.3.0 version, BAM Dashboard

The following error occurs constantly in BAM composer
'an error had happened see the logs' and contact administrator.

and in the log files the following error is observed:

[bam_server2] [WARNING] [] [oracle.adfinternal.view.faces.context.RichExceptionHandler] [tid: [ACTIVE].ExecuteThread: '13' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 922f9c8e-3f32-45a9-b4fc-17048868b929-0001ee2f,0] [APP: BamComposer] [partition-name: DOMAIN] [tenant-name: GLOBAL] [DSID: 0000M7pm5402zGCpJCp2if1QYhPM00000E] ADF_FACES-60098:Faces lifecycle receives unhandled exceptions in phase RENDER_RESPONSE 6[[
javax.el.ELException: java.lang.reflect.UndeclaredThrowableException
at javax.el.BeanELResolver.getValue(BeanELResolver.java:367)
at com.sun.faces.el.DemuxCompositeELResolver._getValue(DemuxCompositeELResolver.java:176)
at com.sun.faces.el.DemuxCompositeELResolver.getValue(DemuxCompositeELResolver.java:203)

..

Caused by: java.lang.reflect.UndeclaredThrowableException

..

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'

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