Implication Of Having OEM Monitor User Privilege To Change The Thread Rule In JVMD Page
Last updated on APRIL 18, 2018
Applies to:APM - Application Performance Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
What is the implication of the OEM user having the following privileges?
1) Monitor user is able to make any running threads to idle on a weblogic managed server where JVMD agent is deployed
2) Monitor user is able to mark any normal thread as a system call which can increase the priority of the thread making other threads to go back to waiting reducing the performance of server
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