java.lang.RuntimeException: oracle.soa.management.facade.DataSetTooLargeException: Requested audit trail size is larger than threshold 1048576 chars

Error :- Unable to display Flowtrace due to exception while initializing object, please review logs for detailed information.

>> 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)
>>> at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
>>> at oracle.soa.management.internal.ejb.impl.FacadeFinderBean_4vacyo_FacadeFinderBeanImpl_1036_WLStub.getAuditTrail

(Unknown Source)

Cause – For some of the heavy processes, we saw that audit trail trace size grow above the allowed max size and  during instance audit trail we are seeing this error.
Resolution :-

11.2.3 instanceTrackingAuditTrailThreshold

This parameter is used to limit the audit trail size while it is being built. The default value is 1MB. If the audit trail exceeds the instanceTrackingAuditTrailThreshold size (1MB by default), then an exception is thrown, and the audit trail is not fully built. The value is in Bytes, so the default value is 1024*1024. This parameter can improve performance, as it prevents huge audit trails to potentially consume a lot or all the memory available on the SOA server where the audit trail is built. So in many way it acts as a safety valve. However in some cases users might want to increase the default value, if they get an exception while retrieving audit trails from Enterprise Manager, that states the ” instanceTrackingAuditTrailThreshold” has been exceeded.

audittrial
Advertisements
This entry was posted in SOA, Weblogic. Bookmark the permalink.

2 Responses to java.lang.RuntimeException: oracle.soa.management.facade.DataSetTooLargeException: Requested audit trail size is larger than threshold 1048576 chars

  1. Hello! Did you have to restart the server? Because we’ve updated that parameter but the error did not go away…

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s