My Oracle Support Banner

E1: ORCH: Long Running Synchronous UBEs (Job Execution Time More Than 10 Minutes) Causing the Stuck Threads in WebLogic Server (Doc ID 2769326.1)

Last updated on FEBRUARY 06, 2024

Applies to:

JD Edwards EnterpriseOne Orchestrator - Version 9.2 and later
JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When Orchestration runs a job that takes more than 10 minutes time to complete following stuck threads call stacks are generated in the WebLogic Server logs, however the both the jobs completes successful without any error.

<WLSHome>\user_projects\domains\<domain_name>\servers\<AIS_server_name>\logs\<instancename>.log shows below errors :

<[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <b2b75020-1c70-41f0-9256-3035e79d9276-00000013> <1615967925884> <[severity-value: 8] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-000337> <[STUCK] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "625" seconds working on the request "Http Request Information: weblogic.servlet.internal.ServletRequestImpl@2bfd2de4[POST /jderest/studio/client/orchestrator/ORCH_Name]

", which is more than the configured time (StuckThreadMaxTime) of "600" seconds in "server-failure-trigger". Stack trace:

sun.misc.Unsafe.park(Native Method)

java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)

java.util.concurrent.FutureTask.awaitDone(FutureTask.java:429)

java.util.concurrent.FutureTask.get(FutureTask.java:191)

com.oracle.e1.rest.orchestrator.thread.JobQueue.submitSynchOrchestration(Unknown Source)

 

 Steps -

  1. Create and Orchestration and run a UBE via Report Service which has child UBE.
  2. Once the parent UBE completed successfully, the child UBE is run which takes more than 10min to complete as it has run synchronously.
  3. Both the UBEs completes successful.
  4. Review the WLS <instancename>.log for below mentioned stuck thread errors.

Example -  Orchestration first submits batch job R3482 and If job complete successfully, it will then submit next batch job R3483 (synchronously).

Changes

 

Cause

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
Symptoms
Changes
Cause
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.