Last updated on JANUARY 15, 2016
Applies to:APM - Application Performance Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
The following scenario may prevent BTM from successfully starting:
You have a BTM monitor running but not otherwise accessible for some reason. For example:
- There may be an excessive number of threads running in WebLogic that prevent the BTM threads from running/responding.
- There may be HUNG/BLOCKED/HOGGING threads that prevent BTM threads from running.
- There may be a bug in BTM that is locking it up.
Please note that in the above scenario the BTM Monitor process has been started and it is running but it is not responding. Under these circumstances a WebLogic instance running a BTM observer that accesses that monitor may fail to start.
In other words, a hung BTM monitor will impact a BTM observer and may prevent it from successfully starting.
It is important to note that if the BTM monitor process is NOT running then the observer and the WebLogic instance it is running within will startup OK. This problem ONLY happens when the BTM monitor is running but in an unresponsive state.
There is a difference in behavior between a NOT running BTM monitor and a BTM Monitor that is running but is NOT RESPONSIVE.
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