Stuck threads Error and java.net.SocketException: Write failed: Broken pipe (Doc ID 2235757.1)

Last updated on OCTOBER 12, 2023

Applies to:

Symptoms

On : 11.1.11.1.0 version, Performance

Customer having the performance issue in the general ledger server, the following error occurs.

There many stuck threads in the General Ledger due to the following error

ERROR
-----------------------
[2017-02-17T17:38:21.526+00:00] [GeneralLedgerServer_1] [ERROR] [] [oracle.EPMOHPS] [tid: [STUCK].ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: MCELIS] [ecid: 005IBngE7RAA9T55vRH7iX0001bS000pgc,0:4] [APP: LedgerApp#V2.0] [DSID: 0000LdD2IQWA9T55vRCCyX1OZ5fR002mEZ] No se puede get olap application Information. Error de Essbase(1051030): La aplicación XCC_BETH no existe.[[
com.essbase.api.base.EssException: No se puede get olap application Information. Error de Essbase(1051030): La aplicación XCC_BETH no existe.
at com.essbase.server.framework.EssOrbPluginDirect.ex_olap(Unknown Source)
at com.essbase.server.framework.EssOrbPluginDirect.essMainGetApplicationInfo(Unknown Source)
at com.essbase.api.session.EssOrbPlugin._invokeMainMethod(Unknown Source)
at com.essbase.api.session.EssOrbPlugin._invokeMethod2(Unknown Source)
at com.essbase.api.session.EssOrbPlugin._invokeMethod(Unknown Source)
at com.essbase.server.framework.EssOrbPluginDirect._invokeProtected(Unknown Source)
at com.essbase.api.session.EssOrbPluginEmbedded.invokeMethod(Unknown Source)

Additional Errors :

[STUCK].ExecuteThread:

java.net.SocketException: Write failed: Broken pipe

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Access General ledger pages

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot Access General ledger pages

Cause

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