PATCHBAY DROPS MESSAGES - Unable to commit transaction::commit transaction exception - transaction.RollbackException (Doc ID 2273595.1)

Last updated on JUNE 16, 2017

Applies to:

Oracle Commerce Platform - Version 10.1.2 and later
Information in this document applies to any platform.

Symptoms

When servers ran out of inodes (inodes is UNIX specific, but the underlying symptom is exhaustion of resources) due to search index failure, it affected transaction handling for Oracle Commerce Platform (ATG) JMS messaging systems.. This then affected their transaction handling and JMS messaging systems on ATG instance. Messages appear to be left on the queue after a transaction was unable to be committed. This was being caused by JMS messages not sending and then not rolling back properly and then re-sending, essentially creating a loop that uses up resources sending these JMS messages until the server runs out of resources.  

You may see the following type of errors/exceptions.

Transaction Rollback Exceptions in logs:

Changes

 N/A

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms