Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
The current implementation of derby based JDBC channel uses a single table for storing events. When subject to excessive load all the DML operations happening on this table will lead to lock contention and escalation, thereby impacting the performance of the system.
It is preferable that the events be distributed over multiple tables so that the overall contention for DML is reduced.