My Oracle Support Banner

Business Intelligence Publisher 11.1.1.7.171017 Reports Fail With Error 'BEA-310006 Critical Subsystem core has failed. Setting server state to FAILED. Reason: Thread deadlock detected' (Doc ID 2496029.1)

Last updated on FEBRUARY 03, 2019

Applies to:

BI Publisher (formerly XML Publisher) - Version 11.1.1.7.x and later
Information in this document applies to any platform.

Goal

Business Intelligence Publisher 11.1.1.7, Enterprise Administration System Configuration related issues

 

 

 

Users report the following intermittent error with BI Publisher for version 11.1.1.7.171017:

    <BEA-310006> <Critical Subsystem core has failed. Setting server state to FAILED. Reason: Thread deadlock detected>

The following document shows <Patch

<Note 2016885.1> - Reports Fail With ' [deadlocked thread] [ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default (self-tuning)' Errors (Doc ID 2016885.1)

However for this customer site. the requirement is for a patch to fix the issue on the latest PSU for july 2018.
 

Solution

To view full details, sign in with your My Oracle Support account.

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


In this Document
Goal
Solution
References


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