APEX

Hi,

After upgrading to Apex 3.1 we have started getting a significant number of deadlock errors.

Has anybody experienced this ?
Any suggestion ?

Here is the trace file:
DEADLOCK DETECTED
[Transaction Deadlock]
Current SQL statement for this session:
DELETE FROM WWV_FLOW_DATA WHERE FLOW_INSTANCE = :B1 AND ITEM_ID IN (SELECT ID FROM WWV_FLOW_PAGE_PLUGS WHERE FLOW_ID = :B3 AND PAGE_ID = :B2 AND PLUG_SOURCE_TYPE IN ( 'SIMPLE_CHART', 'UPDATABLE_SQL_QUERY', 'DBMSSQL_CURSOR', 'FUNCTION_RETURNING_DBMSSQL_CURSOR', 'FUNCTION_RETURNING_SQL_QUERY_CACHED', 'FUNCTION_RETURNING_SQL_QUERY', 'STRUCTURED_QUERY', 'SQL_QUERY', 'DYNAMIC_QUERY'))
----- PL/SQL Call Stack -----
object line object
handle number name
0x6e1b8384 227 package body FLOWS_030100.WWV_FLOW_DISP_PAGE_PLUGS
0x78effc2c 10194 package body FLOWS_030100.WWV_FLOW
0x6e66b284 255 procedure FLOWS_030100.F
0x6c34b6fc 10 anonymous block
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-0025002f-00001aa3 43 458 X 75 373 X
TX-00010005-00035c1e 75 373 X 43 458 X
session 458: DID 0001-002B-00000D95 session 373: DID 0001-004B-00002FC5
session 373: DID 0001-004B-00002FC5 session 458: DID 0001-002B-00000D95
Rows waited on:
Session 373: obj - rowid = 00034250 - AAA0JQAAFAAE4zCAAb
(dictionary objn - 213584, file - 5, block - 1281218, slot - 27)
Session 458: obj - rowid = 00034250 - AAA0JQAAFAAE4zCAAa
(dictionary objn - 213584, file - 5, block - 1281218, slot - 26)


Thanks
Roelie Viviers