In OpenEdge 11.6 the method of retrieving metric values for OS resources was changed from a JNI implementation to WMIC. The "WMIC" stands for Windows Management Instrumentation Command-line. These messages are simply recording the command line that was running and the exception or timeout that was reached which failed.
Additionally, the osmetrics code for Windows which accessed the Windows registry entries was completely replaced by a combination of standard java/WMIC calls in OpenEdge 11.6. As a result, osmetrics (on Windows only) no longer accesses the registry entries and this conflict no longer occurs when another Service uses performance counters.
For example, In Windows OEM uses "wmic <pid>" call terminate command, on other platforms it uses osmetrics
For example: The timeout messages would be related to a time that the Adminserver is not reachable, there's usually a pre-ceeding message in the admserv.log
Error registering with Admin Server. (8845)
The command syntax listed in these WMIC admserv.log messages can be useful to further diagnose issues on the system at the time.
- you could find the Processid numbers referred in the Task Manager
- you could run precisely the "Command" information recorded from a command prompt:
wmic Process where (Processid=10460 or Processid=6836)