BTM Ignores Observer Size Limit, Creating Big Objects Under EJB Probe

(Doc ID 2191424.1)

Last updated on OCTOBER 17, 2016

Applies to:

APM - Application Performance Management - Version to [Release 12.1]
Information in this document applies to any platform.


Business Transaction Management (BTM) server: Release
Observer: Build Info:

A custom java application is bing monitored with with BTM.
A production outage was encountered because of big objects in a heap created by BTM observer.
Server went to OutOfMemory and created heap dumps.

Observer policy > Maximum message size limit was set to default value 2MB. but the heap dump generated has about 20 objects of sizes: 150MB, 80MB down to 18MB.





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