none
Increased CPU usage after enabling a MSMQ 2003 MP Monitor RRS feed

  • Question

  • Hello,

    We recently imported the MSMQ 2003 MP and enabled the "Number of Messages"-monitor for a number of private queues on one server, however after doing this the CPU usage on that server has increased dramatically. The server is running Server 2003, x86, 2GB of RAM and it's virtual. The Windows Script Engine Version is 5.7.

    The Ops Manager Event Viewer is spamming these, all with different instance id's:

    Forced to terminate the following process started at 12:05:26 because it ran past the configured timeout 300 seconds.

    Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "QueueStatistics.vbs" server.domain.local false

    Working Directory: C:\Program\Microsoft Monitoring Agent\Agent\Health Service State\Monitoring Host Temporary Files 6\3397\

    One or more workflows were affected by this.

    Workflow name:

    Microsoft.MSMQ.2003.Monitor.QueueMessageCount.Baseline

    Instance ID:

    server\private$\work-customer2cs

    Don't know what to do really, except for raising the timeout to maybe 380-400 seconds. Im thinking that the server has too low specs for this, or am I wrong? Help and support appreciated. :)

    Tuesday, September 30, 2014 11:05 AM

Answers

  • Hi,

    I agree with you, it is suggested to use overrides to increase the timeout value. After enable this monitor, it also increase the CPU usage of the server. As we can see, this Windows 2003 x86 virtual machine may have performance issue. Why not upgrading it to new version.

    Regards,

    Yan Li


    Regards, Yan Li

    Wednesday, October 1, 2014 2:26 AM
    Moderator