My Oracle Support Banner

WebLogic resources become disabled which causes engine to stop processing (Doc ID 796418.1)

Last updated on JANUARY 20, 2020

Applies to:

Oracle Business Process Management Suite - Version 6.0.4 and later
Information in this document applies to any platform.
***Checked for relevance on 23-Mar-2012***
***Checked for relevance on 30-August-2013***

Symptoms

The engine or workspace will appear to run fine initially, but after a short (or maybe long) period of time all of a sudden it appears that nothing is moving forward.

If you examine the engine logs you may see some exceptions that initially look like:



"[ACTIVE] ExecuteThread: '103' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.jdbcx.base.BaseXAConnection@1b44c86 BLOCKED
weblogic.jdbcx.base.BaseXAConnection.getXAResource(Unknown Source)
weblogic.jdbc.wrapper.XAConnection.getXAResource(XAConnection.java:455)
weblogic.jdbc.jta.DataSource.end(DataSource.java:795)
weblogic.transaction.internal.XAServerResourceInfo.end(XAServerResourceInfo.java:1232)

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

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