Why does the CPU usage reach 100 per cent on our machine running Active Configuration Client?
Under some conditions the Active Configuration Client loops, causing 100% CPU utilization when processing configuration data from the Active Configuration Server. This is most likely to occur when configuration keys (data names) are duplicated or are the same as section keys (names). An upcoming release will resolve these issues. Until then, please use unique names for all section and configuration keys within an application.
Related Questions
- When running Jaws PDF Server as a service, Why can I only convert files sent from a client machine, when logged on with an administrator account?
- Why does the CPU usage reach 100 per cent on our machine running Active Configuration Client?
- What is the recommended configuration for the hard disk of a machine running the pSPT?
