[SIM 6.1] WCCAgents process memory usage

[Danilo B]

Hi all,

Is it fine that WCCAgents.exe process uses about 700 MB or ram? What about this process? Operating System is Windows Server 2003 x86 Standard with SQL Server Express 2008. SIM version 6.1 is monitoring about 300 objects.
MXDomainmgr process is using about 700 MB of ram too.

Thank you all for help.

[BPE]

6-8 Mb peak memory is normal at our installation. But perhaps you have a problem with a big windows event log.
Are you sure that your webes is working correct? Open your webes interface at https://your_server:7906
user admin and check the notification.

I guess you have HW service contracts with 300 objects. You should open an HP Insight remote support call at HP over your HW contract.
select HW repair -> HW Type: Remote Support / Tools inside itrc call manager.

[Danilo B]

Hi bpe,

thank you for help. Eventlog is clear, notification is 'on' for HP SIM HP Remote Support and Email, and they are all 'green'. Other notifications are off.

Any idea?

Regards, Danilo

[BPE]

Have you tested your installation with wccproxy test? You should get an email and a service event in HP SIM. If you have a big delay (greater an hour) until you see the service event something is wrong with the eventlog handling.

If you get the service event in less than an 15 minutes. You should try a restart of the wccproxy service an check the memory consume over time with the task manager or process explorer.
e.g. I would check the lower plane in the process explorer for possible hints(many handles are generated but never closed).

Do you have devices which are behind firewalls? Perhaps some parts of the communication are blocked and lead to memory allocation until the timeouts happens.

Because mxdomainmgr has a similar behavior
you can perhaps also find some hints in the SIM logfiles.

[Danilo B]

wccproxy test did not result in any email or service events in HP SIM in an hour. So I restarted the wccproxy service. After restart WCCAgents process was about 5 MB slowly increasing by about 4KB each step.

Most of the devices are behind one or two firewalls but traffic is allowed by any-any rules from/to HP SIM server.

Thank you for support!

[BPE]

Today I saw a very similar behavior with windows 2008 R2 and windows firewall activated.
The firewall blocked the name resolution inside the WEBES desta_service and could not connect to the WCCAgent. The Agent was working normal but the data could not be passed to WEBES. This could be an explanation for memory consummation. This is also problem if you have name resolution problems. But you should find indication for the problems in your svctools\spesific\desta and webes \logs directory files.

[BPE]

Today I saw a very similar behavior with windows 2008 R2 and windows firewall activated.
The firewall blocked the name resolution inside the WEBES desta_service and could not connect to the WCCAgent. The Agent was working normal but the data could not be passed to WEBES. This could be an explanation for memory consummation. This is also problem if you have name resolution problems. But you should find indication for the problems in your svctools\specific\desta and webes \logs directory files.

[Danilo B]

Hi,

desta service log (P:\Program Files\HP\svctools\specific\desta\logs\HealthCheck.log) report many errors like this:

---------- Webes HealthCheck Problem Reported at gio, 16 set 2010 07:05:04 +0200 ----------

Subject: Webes HealthCheck End-To-End Detection Failed

Webes Health Check reported a problem at gio, 16 set 2010 07:05:04 +0200

Hostname: vsim-01.bitfarm.pri
Version: Web-Based Enterprise Services Common Components for Windows V6.1 (Build 136), member of Web-Based Enterprise Services Suite for Windows V6.1 (Build 136)
Error Code: E2E

Description:

Webes failed to analyze a HeartBeat Event and log a problem report. Webes may not be in a running state.

CallStack:



Recommended Action:

Stop and restart Desta_service. If this problem persists then run "desta sysinfo" on the command line and give the generated Zip file to HP Customer Support.

Thank you for help!

[Danilo B]

Hi,

please note Operating System is Windows Server 2003 Standard x86 with firewall disabed.

Regards, Danilo

[BPE]

You can also try "desta status" to see if the desta service is still running. Perhaps the installation of postgresql failed. Postgresql is included with WEBES since 5.6. If the database connection is not possible desta_service will stop after some time.
This would also explain why your wccproxy is increasing. Desta_service / WEBES will be not able to read the logs from wccproxy because the initialization never ended.