WLSDM log viewer line limit is 1000 but you can search any string and find searched string where line is located in whole log file via “text filter”.
There is another way to view log files via WLSDM file explorer. Go to “Operational Tools & Utils -> File Explorer” pick “.log” file then click view button (max 1 mb view size). Also you can download log file to your local environment via file explorer.
You can change access restriction configuration in “WLSDM System Settings > system.authorization” page.
Default value is OFF in “system.authorization.page.access.fileexplorer.allgroups” feature. It means only administrators can access to “file explorer”. If you turn on this feature, you must set access path for non-adminstrator users then non-adminstrator users only can access the path(s).
You can restrict log viewer access configuration via “system.authorization.page.access.logviewer”. Default value is on, it means all users can access log viewer, if you turn off this feature, non-adminstrator users will not able to access logviewer. 56.jpg
On the other hand, Make sure you have not applied wlsdm_agent JVM arguments to the AdminServer?
If you send the whole details and logs we would like to help you to alter this problem. We have never seen this error before. It looks like this is something relevant to this environment. Have you tried the installation on another domain environment?
Probably it is a WebLogic issue. If it is a “Devlopment Mode” WebLogic domain; you should not see the “Change Center” in WebLogic console. But, in your sceen capture “WebLogic Change Center” is available (attached below). We are recommending to setup your WebLogic domain from scratch as Development mode domain.
Are you sure you have created HTTP transactions for the relevant managed server? Remember you need to create real traffic to exceed 8kb buffer size for the response times monitoring. So, at least there must be +100 request after managed server restart.
Are you sure you have selected the right managed server on the “Response Times” page? (Please take below screen capture as a reference)
First of all your WLSDM version is not the latest; please upgrade to v3.4.1 (it will took about 5 min). Please do a fresh installation. This domain was open for all the metrics about “STORE DATA” feature. That’s why you faced this issue.
Let us analyze more. Is this thread is in ManagedServer or AdminServer? We need below information to help you.
Could please at least take 3 thread dump for AdminServer and ManagedServer then send us to us? (thread dump: kill -3, or from WLSDM console)
Could you please zip all WLSDM log files and send to us? (Available at WLSDM\logs folder)
Could you please runt this command and share the output with us?
du -sh *
Could you please share the WLSDM version?
We are suspecting about data archive. As a workaround please DISABLE all your (make OFF) data archive settings. Go to “System Settings > system.archive (tab)” page and OFF all archive settings if they are currently ON. Then restart only AdminServer then observe the new states about high CPU consumption.