-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
False
-
NEW
-
NEW
-
Customer is trying to clear DB tables using LogCleanupCommand but its failing with transaction timeout:
WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffff64401459:1e9992f0:61f8f765:1267628 in state RUN WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 1) ARJUNA012095: Abort of action id 0:ffff64401459:1e9992f0:61f8f765:1267628 invoked while multiple threads active within it. WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 1) ARJUNA012381: Action id 0:ffff64401459:1e9992f0:61f8f765:1267628 completed with multiple threads - thread EE-ManagedThreadFactory-default-Thread-1 was in progress with java.base@11.0.12/java.net.SocketInputStream.socketRead0(Native Method) java.base@11.0.12/java.net.SocketInputStream.socketRead(SocketInputStream.java:115) java.base@11.0.12/java.net.SocketInputStream.read(SocketInputStream.java:168) . .. .
Customer is facing this issue while removing records from process audit table, here is the number of entries in process audit table:
rhpam=# select count(*) from rhpam.nodeinstancelog; count ---------- 46737161 (1 row) rhpam=# select count(*) from rhpam.variableinstancelog; count ---------- 23320841 (1 row) rhpam=# select count(*) from rhpam.processinstancelog; count ---------- 1406879 (1 row)
Customer tried using 'RecordsPerTransaction=100' but still its failing with transaction timeout. Seems RecordsPerTransaction param is not working as expected.
- clones
-
RHPAM-4184 Transaction timeout reported even if RecordsPerTransaction param is used in LogCleanupCommand
- Closed