thanks for the reply
Is this specifc to a server or for all the servers under the domain ? It was not configured knowingly anyway.
Is there any way to disable it from console, rather than the config file changes?
I checked it more on the diagnostics part, and it is defenitely the diagnostics that creates this issue with one of my managed server which size upto huge 150GB under the server/data/store/diagnostics folder.
but the other managed server diagnostics data size looks fine .
could you please give me some poniter to get rid of this unwanted diagnostics data getting created for the managed servers.
We first need to understand why the diagnostic information is being collected on that particular server.
Please check what is WLDF watch/rule or collection configured for in your environment.
May be there is an issue on that server due to which it is collecting huge data. If I have further details, I might be able to help.
Please find the below diagnostic module config fom the condig.xml
This configuration was present earlier also, but it looks like the logs statrted accumulating recently due to some other changes made to console. There is nothing coming under the WLDF console extension in server admin console.
Other than changing the start script, will it be fine to go the file location ./server/data/store/diagnostics/WLSDIAGNOSTIC**.DAT and delete the older file while the server is running now?
Incase not posisible , an example on the change in startscript and the config.xml will b helpful
I am not really comfortable suggesting you to delete the WLSDIAGNOSTIC**.DAT files for a running server.
If you have restarted the server and the files were from the previous run then you can delete them.
The JDBC connection pool might have been targeted to both the servers. So, then why the collection is high on only one managed server.
Is it possible that there is some issue with the JDBC Connection Pool on that server?
Can we check and try to fix it. I believe that will be the best way forward.