I am facing an Out of Memory situation owing to a large number of File handles being created while writing the Diagnostics file located under /server/<server-name>/data/diagnostics
I have <preferred-store-size> configured at 100MB, however the file seems to grow to about 2GB in size, even when DataRetirementEnabled is enabled(default).
I have stopped the file size growth by setting the following param in the startup script:
-Dcom.bea.wlw.netui.disableInstrumentation=true but has the following questions:
Why does the file size grow to ~ 2GB and stop or rotate after that? Do we have some sort of hard limit for WLS_DIAGNOSTICS.DAT file and if so, why is it set to 2 Gigs?
I would like to read the contents of the diagnostic file, for which we have tried to export the diagnostics archive using the WLST offline option exportDiagnosticData() but we can’t seem to make any sense out of the resultant xml files. They are either empty templates or unreadable binary files. Is there some way we can create some file which will give us data with timestamps so as to see when the data was updated in the .DAT file?
Here’s the command we used:
exportDiagnosticData(logicalName='HTTPAccessLog', logName='WLS_DIAGNOSTICS000000.DAT', exportFileName='myExport.xml', beginTimestamp=0, storeDir='/local/apps/oas/tms/servers/tms1/datbak')