BPEL Application Spawns Numerous Database Connections Causing It To Crash

Oracle(R) BPEL Process Manager - Version: 10.1.2.0.2

Symptoms
You are running Oracle BPEL application connected to Oracle Databases. There is a poller, which poll the DB for requests inserted by your request engine, these pollers then fire the relevant BPEL process for each request.

During runtime, your application started spawning database connections within minutes, causing it to crash. There are no error messages written into any log file.

Cause
All the concurrent active sessions and the sessions being spawned are waiting on the same resource and throwing the same DB error : ORA-04021: Timeout Occurred While Waiting To Lock Object.

This is a known BPEL PM bug

Bug 5001394 - BYTE OFF MAKES BPEL HANG ON AUDIT_TRAIL, AUD TABLE LOCK & CALLBACK MESG LOST
.
Bug 5001394 - BYTE OFF MAKES BPEL HANG ON AUDIT_TRAIL, AUD TABLE LOCK & CALLBACK MESG LOST
.
Solution
To implement the solution, please execute the following steps:

Apply patch for Bug 5001394. Run the test again

References
Bug 5001394 - 1- BYTE OFF MAKES BPEL HANG ON AUDIT_TRAIL, AUD TABLE LOCK & CALLBACK MESG LOST
Errors
ORA-4021 time-out occurred while waiting to lock object

Comments

Popular posts from this blog

ORA-44412: XE edition memory parameter invalid or not specified

How to mount a WD Book Live as NFS in OEL6U3

BPEL Engine Exceptions ORABPEL 02000 - 02179