ï§ What is the scope of this knowledge?
This applies only if customer is using SDM 7.63 version and up.
ï§ What is the error?
org.apache.cxf.phase.PhaseInterceptorChain : Chain org.apache.cxf.phase.PhaseInterceptorChain@552f37ae was created. Current flow:
Could not roll back Hibernate transaction; nested exception is org.hibernate.TransactionException: Unable to rollback against JDBC Connection
This is not the only way to fix the issue. You would check if you have CLOB or BLOB fields and large data in tables, this will overflow current parameters ruling BF on execution.
Customer was facing issue with AQS cache. The reason is that the customer was having CLOB column in the table & since CLOB is larger data type which can contain a lot of memory per row (example: In oracle CLOB column can be up to 4GB) it was running out of memory for big tables.
ï§ What is the way to attach this issue to try to see if this works?
1) Reduce the batch size for SDM In-memory AQS cache processing by reducing "lw2.insert.batchSize" in outerbay.properties file.
However this did not help and after a remote session we got to know that the csv file in the archive folder was very big more than 32GB each. So we had suggested for an additional change.
2) Reduce the file batch size, this can be configured in System Parameter -> Database to File -> Performance -> "Data Movement Batch Size". And after this rerun the Archive Job & AQS cache.
ï§ What else to read or as reference?
No other information, this is one way to attack the issue, most of the times it is related to issue stated here and the wat to fix it up, but, if before solution fails, then you have to continue troubleshooting in other way.