LMS 3.2 : issue with custom portal : high CPU

Unanswered Question
Sep 7th, 2010

Hi,

Customer has a big issue with LMS.

When he connects to the standard portal, it works fine.

pdshow seems ok.

But when he wants to work with custom portal (portal.jpg), it makes a long time to display information and when he wants select something it hangs.

CPU is very high. He must stoped/restart LMS to have a normal CPU.

I asked him to :

- restart LMS, he made at 14h30
- CPU was ok and he worked with standard portal withou problems but when he tried to put debug for portal CPU increase at 15h30:

Common Services -> server -> Admin ->  CS Log Configurations: debug on CiscoWorks Portal, CiscoWorks portlets and CS Home

Process which takes a lot of CPU is tomcat, you will find pdshow.txt, stdout.log and stderr.log.

He tries to go to the custom portal but it hangs, you will find logs from debug : CSHomePage.log and CSPortal.log

he sent me AAD.log because there was " high severity alert".

Many thanks for your help,

Elisabeth

Attachment: 
I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Sat, 09/11/2010 - 17:38

The most obvious problem is that DfmBroker is down.  Check to make sure tcp/9002 is not in user, then try a server reboot.  See if the AAD problems go away (and perhaps the CPU problem will as well).  If not, post the NMSROOT/objects/local/logs/broker.log.

Actions

This Discussion