SOA Tips & Tricks Series: Preventing OOM Exceptions with Very Large Audit Trails

Introduction

In very complex flows, the audit trail or flow trace sizes can grow above the limit where the EM console can display them correctly with the default settings. The reason for these default settings is to avoid generating huge audit trail objects in memory and thus potentially causing OOM errors – therefore the standard limit is set to 1 MB.

Main Article

You will see the following exception in a case where the audit trail exceeds this limit:

Exception occured while retrieving the Flowtrace XML for the Composite Instance; ECID: 9c37958941ffc184:-3503c179:138e19ea68a:-8000-0000000000002ee6
 java.rmi.RemoteException: EJB Exception: ; nested exception is:
 java.lang.RuntimeException: oracle.soa.management.facade.DataSetTooLargeException: Requested audit trail size is larger than threshold 1048576 chars
 at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:237)
 …

If this is not a design or implementation error (for example an indefinite loop), then you can try to increase this audit trail limit:

instanceTrackingAuditTrailThreshold

You can modify it in the System MBean Browser at the following location:

aiatt2

 

See also http://docs.oracle.com/cd/E25178_01/core.1111/e10108/others.htm Chapter “11.2.3 instanceTrackingAuditTrailThreshold” for details.

Add Your Comment