<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Mxdomainmgr.exe Memory Spike in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158975#M301</link>
    <description>I shouldnt call it a spike, it will eat up 400MB + for hours, then release.  Id call it a leak, but it eventually clears itself... Does anyone else have this issue?  This is a relativley small installation.</description>
    <pubDate>Wed, 07 Jan 2004 23:44:41 GMT</pubDate>
    <dc:creator>Adam Levinson</dc:creator>
    <dc:date>2004-01-07T23:44:41Z</dc:date>
    <item>
      <title>Mxdomainmgr.exe Memory Spike</title>
      <link>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158973#M299</link>
      <description>i recently upgraded to SIM 4.00.  soon after, i started having memory spikes from a process with the name mxdomainmgr.exe . is this process related to SIM?  i have one other app that runs on the server, and has been for a while, and i cannot track the source of this executable.&lt;BR /&gt;&lt;BR /&gt;thx.&lt;BR /&gt;adam</description>
      <pubDate>Wed, 07 Jan 2004 19:26:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158973#M299</guid>
      <dc:creator>Adam Levinson</dc:creator>
      <dc:date>2004-01-07T19:26:27Z</dc:date>
    </item>
    <item>
      <title>Re: Mxdomainmgr.exe Memory Spike</title>
      <link>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158974#M300</link>
      <description>I've seen various mx prefixed programs on our HPSIM Server including the one you mention. And at times, especially during discovery, they're pretty busy.&lt;BR /&gt;So, yes I'd say it is an HPSIM Program.</description>
      <pubDate>Wed, 07 Jan 2004 21:55:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158974#M300</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2004-01-07T21:55:52Z</dc:date>
    </item>
    <item>
      <title>Re: Mxdomainmgr.exe Memory Spike</title>
      <link>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158975#M301</link>
      <description>I shouldnt call it a spike, it will eat up 400MB + for hours, then release.  Id call it a leak, but it eventually clears itself... Does anyone else have this issue?  This is a relativley small installation.</description>
      <pubDate>Wed, 07 Jan 2004 23:44:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158975#M301</guid>
      <dc:creator>Adam Levinson</dc:creator>
      <dc:date>2004-01-07T23:44:41Z</dc:date>
    </item>
    <item>
      <title>Re: Mxdomainmgr.exe Memory Spike</title>
      <link>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158976#M302</link>
      <description>Adam -&lt;BR /&gt;&lt;BR /&gt;This process spikes up pretty high for an extended period of time anytime a scheduled task is ran. It eventually cleans itself up so I would say that it is normal. That's one of the reason why HP recommends a machine with Fast CPU and lots of memory.</description>
      <pubDate>Thu, 08 Jan 2004 17:33:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158976#M302</guid>
      <dc:creator>Jadrice Toussaint</dc:creator>
      <dc:date>2004-01-08T17:33:21Z</dc:date>
    </item>
    <item>
      <title>Re: Mxdomainmgr.exe Memory Spike</title>
      <link>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158977#M303</link>
      <description>Since it cleans up after itself, I would not call it a memory leak.</description>
      <pubDate>Thu, 08 Jan 2004 17:33:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158977#M303</guid>
      <dc:creator>Jadrice Toussaint</dc:creator>
      <dc:date>2004-01-08T17:33:58Z</dc:date>
    </item>
    <item>
      <title>Re: Mxdomainmgr.exe Memory Spike</title>
      <link>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158978#M304</link>
      <description>Agreed.  But prior, CIM 7 had been running on that server for a long time in the same capacity and Ive never had this issue.  The only task besides the defaults that I created, is one to forward Critical event notifications, thats it.  I dont think that process should be eating up 400 + MB, with an installation that has less then 40 devices, and for hours at a time...</description>
      <pubDate>Thu, 08 Jan 2004 17:41:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158978#M304</guid>
      <dc:creator>Adam Levinson</dc:creator>
      <dc:date>2004-01-08T17:41:05Z</dc:date>
    </item>
    <item>
      <title>Re: Mxdomainmgr.exe Memory Spike</title>
      <link>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158979#M305</link>
      <description>I have same problem with my installation. This is really annoying.&lt;BR /&gt;&lt;BR /&gt;Regards.&lt;BR /&gt;Jani&lt;BR /&gt;</description>
      <pubDate>Mon, 02 Feb 2004 07:34:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158979#M305</guid>
      <dc:creator>Jani Metsäkonkola</dc:creator>
      <dc:date>2004-02-02T07:34:25Z</dc:date>
    </item>
    <item>
      <title>Re: Mxdomainmgr.exe Memory Spike</title>
      <link>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158980#M306</link>
      <description>I have a case open with HP on this issue.  I will post what we have so far here:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=349387" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=349387&lt;/A&gt;</description>
      <pubDate>Mon, 02 Feb 2004 12:42:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/mxdomainmgr-exe-memory-spike/m-p/3158980#M306</guid>
      <dc:creator>Tim McGue</dc:creator>
      <dc:date>2004-02-02T12:42:19Z</dc:date>
    </item>
  </channel>
</rss>

