I've got 3 x3650 servers with Win2008x64 installed. IBM Systems Director is deployed on the first one. Other x3650 servers are monitored via DCOM protocol (so, no agents) and via IMM-modules. There are few simple devices (switches) too. It works like a charm. But after rebooting one server (without ISD installed) ISD consumes 100% CPU. Just see my first screenshot (it uses only 4 cores, because I've modified CPU affinity. Without modification ISD uses ~50% of ALL cores):
I've looked into java.exe with VisualVM to see, which threads are consuming so much CPU, and detected, that threads "RMI TCP Connection(..) - 127.0.0.1" are consuming all the CPU.
Does anybody has had the same problem? Maybe it's JRE problem?
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
4 replies Latest Post - 2013-02-21T09:47:12Z by SystemAdmin
Pinned topic Systems Director 6.3 uses 100% CPU after server reboot
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-02-21T09:47:12Z at 2013-02-21T09:47:12Z by SystemAdmin
Re: Systems Director 6.3 uses 100% CPU after server reboot2013-02-20T01:33:20Z in response to SystemAdminI have not heard of a RMI TCP Connection thread before. You would need to contact the Help Center for assistance debugging this issue.
IBM Advanced Technical Skills