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

Last updated on JUNE 10, 2016

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:

Caused by: fuego.connector.TransactionException: An error has occurred during the commit. Details : [Caused by 1 exceptions:
weblogic.transaction.RollbackException: Transaction timed out after 31 seconds
BEA1-00C036A7E4BA2F8E1E49
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1782)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:331)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:227)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:283)
at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:277)
at fuego.connector.impl.J2EETransactionCoordinator.commit(J2EETransactionCoordinator.java:55)
at fuego.connector.ConnectorTransaction.commit(ConnectorTransaction.java:406)
at fuego.transaction.TransactionAction.commit(TransactionAction.java:302)
at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:481)
at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
at fuego.server.AbstractProcessBean.runGlobalJmsActivity(AbstractProcessBean.java:2743)
at fuego.server.execution.GlobalJMSExecutor$1.run(GlobalJMSExecutor.java:113)
at fuego.ejbengine.EJBProcessBean.executeTask(EJBProcessBean.java:170)
at fuego.server.execution.GlobalJMSExecutor.execute(GlobalJMSExecutor.java:105)
at fuego.ejbengine.EJBGlobalJMSExecutor.access$400(EJBGlobalJMSExecutor.java:43)
at fuego.ejbengine.EJBGlobalJMSExecutor$JMSExecutorWorker.run(EJBGlobalJMSExecutor.java:213)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:259)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)



After awhile you may notice that the engine continues to connect and is failing due to an exception from weblogic that says the resource is disabled:


An exception occurred while executing a transaction. Details:
Connector [ALBPM_J2EE_RUNTIME_FUEGOLABS_ARG:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].
Detail:Connector [ALBPM_J2EE_RUNTIME_FUEGOLABS_ARG:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].

Caused by: Internal error: Cannot obtain XAConnection weblogic.common.resourcepool.ResourceDisabledException: Pool XAALBPMDS is disabled, cannot allocate resources to applications..

Runtime exception Shell.
Apparent cause :
Connector [ALBPM_J2EE_RUNTIME_FUEGOLABS_ARG:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].
Detail:Connector [ALBPM_J2EE_RUNTIME_FUEGOLABS_ARG:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].




Finally, in checking the thread dumps in weblogic you may find that it looks like a lot of threads are blocked here:


"[ACTIVE] ExecuteThread: '104' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.jdbc.common.internal.ConnectionPool@c2179 BLOCKED
weblogic.common.resourcepool.ResourcePoolImpl.releaseResource(ResourcePoolImpl.java:522)
weblogic.jdbc.common.internal.ConnectionPool.release(ConnectionPool.java:669)
weblogic.jdbc.common.internal.ConnectionPoolManager.release(ConnectionPoolManager.java:113)
weblogic.jdbc.wrapper.XAConnection.releaseToPool(XAConnection.java:395)
weblogic.jdbc.jta.DataSource.removeTxAssoc(DataSource.java:1528)
weblogic.jdbc.jta.DataSource.end(DataSource.java:842)
weblogic.transaction.internal.XAServerResourceInfo.end(XAServerResourceInfo.java:1232)
weblogic.transaction.internal.XAServerResourceInfo.internalDelist(XAServerResourceInfo.java:404)
weblogic.transaction.internal.XAServerResourceInfo.delist(XAServerResourceInfo.java:326)
weblogic.transaction.internal.ServerTransactionImpl.delistAll(ServerTransactionImpl.java:1622)
weblogic.transaction.internal.ServerTransactionImpl.localRollback(ServerTransactionImpl.java:2010)
weblogic.transaction.internal.ServerTransactionImpl.globalRetryRollback(ServerTransactionImpl.java:3009)
weblogic.transaction.internal.ServerTransactionImpl.access$100(ServerTransactionImpl.java:66)
weblogic.transaction.internal.ServerTransactionImpl$1.run(ServerTransactionImpl.java:3230)
weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

"[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)

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms