Exalytics In-Memory Machine X2-4
 
Business Intelligence Suite Enterprise Edition
 

PLA-Support>Eng Systems>Exalytics>Oracle Exalytics>DB: Exalytics_EST
 

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-15616626491>

Applies to:

Symptoms

On : OBIEE, when attempting to access the BI Coreapplication in the FMW EM Farm, the process just hangs and the following error occurs in log files, thus not allowing OBIEE related screens to be accessed and RPD deployment cannot happen.

ERROR
-----------------------
2017-08-29 14:31:25,748 [[ACTIVE] ExecuteThread: '195' for queue: 'weblogic.kernel.Default (self-tuning)'] INFO wls.WLSUtils logp.251 - Error getting application state for application null on server null
javax.management.RuntimeMBeanException: java.lang.NullPointerException
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:205)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:222)
...
2017-08-29 14:31:30,095 [[ACTIVE] ExecuteThread: '195' for queue: 'weblogic.kernel.Default (self-tuning)'] INFO mbean.LockSaveRevertAssistant logp.251 - [EM-02695] Connected to BI Instance; Version: 11.1.1.7.0; Label: BIFNDN_11.1.1.7.0BIBP_LINUX.X64_140515.1014; Build: 20140515_0.
2017-08-29 14:31:32,034 [[ACTIVE] ExecuteThread: '225' for queue: 'weblogic.kernel.Default (self-tuning)'] WARN errPopup.ErrorPopupUtil logp.251 - Write failed: Broken pipe
javax.faces.FacesException: java.net.SocketException: Write failed: Broken pipe
at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:149)
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:189)
at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:193)
at oracle.sysman.emSDK.adfext.ctlr.EMViewHandlerImpl.renderView(EMViewHandlerImpl.java:158)..
...
..
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: java.net.SocketException: Write failed: Broken pipe
at jrockit.net.SocketNativeIO.writeBytesPinned(Native Method)
at jrockit.net.SocketNativeIO.socketWrite(SocketNativeIO.java:46)
at java.net.SocketOutputStream.socketWrite0(SocketOutputStream.java)
....
...
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

Can see the following error in the emoms.log file as well:
2017-08-29 14:31:30,095 [[ACTIVE] ExecuteThread: '195' for queue: 'weblogic.kernel.Default (self-tuning)'] INFO mbean.LockSaveRevertAssistant logp.251 - [EM-02695] Connected to BI Instance; Version: 11.1.1.7.0; Label: BIFNDN_11.1.1.7.0BIBP_LINUX.X64_140515.1014; Build: 20140515_0.
2017-08-29 14:31:32,034 [[ACTIVE] ExecuteThread: '225' for queue: 'weblogic.kernel.Default (self-tuning)'] WARN errPopup.ErrorPopupUtil logp.251 - Write failed: Broken pipe
javax.faces.FacesException: java.net.SocketException: Write failed: Broken pipe

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Log into http://yourserver.com:port/em.
2. Access the Application Deployments, or WebLogic Domain area of the Farm without issue.
3. Next click on Business Intelligence >> Coreapplication and this just hangs. It spins and nothing happens. Cannot monitor OBIEE through EM, and cannot deploy an RPD.

Cause

A log directory was full, causing an inability for the system to write needed logging information to logs and thus the EM login process into the Coreapplication could not complete.

Clearing the directory allowed access to the Coreapplication in EM.

For Example:
.../user_projects/domains/bifoundation_domain/servers/AdminServer/data/ldap

.../user_projects/domains/bifoundation_domain/servers/bi_server1/data/ldap/log

 

Solution

To resolve this issue, take the following steps.

1. Clear out the logs, and archive them if needed to another directory.

2. Do a full restart of the OBIEE system.

3. Now access to the FMW EM Coreapplication can be made.

4. Consider setting up a regularly scheduled process to clear out the ldap log directories. Either manually or through a custom OS level script.
 

References

This solution has no attachment