Windsor
October 29th, 2007, 09:27 PM
Hi all
A client of ours has 5 offices with a server at each office running AD and exchange. The exchange server that handles incoming external email (IBM server dual xeon 3.2GHz, 3GB RAM, Server 2003 R2 SP1) has had a couple of issues lately. two weeks ago (October 16) exchange slowed to a crawl and users were getting constant warning messages that Outlook was trying to communicate with the Exchange server. the problem seemed to be resolved with the next update but the same thing happened again today and again fixed with an update. Thats all ok now, but I noticed last time there was a problem, that xmon was causing the store.exe service to use a constant 25% processor time. restarting just the info store made no difference, but after applying the nod32 update and restarting xmon and the info store, this dropped down to a normal pattern varying between 0 and 10%. I noticed a couple of days later that the info store was back to sitting on 25% CPU load again (but all seemed to be functioning correctly) and it stayed at 25% until the problem we had this morning. Turning off xmon and restarting the info store dropped the usage back to minimal again, and restarting xmon and the info store after the update hasn't caused any increase in CPU load yet. The other 4 exchange servers don't seem to have this issue of high load but they also host fewer mailboxes (80 mailboxes on the problem server and 20-50 on each of the others).
Is this normal behaviour for xmon?
Thanks in advance
Geoff
A client of ours has 5 offices with a server at each office running AD and exchange. The exchange server that handles incoming external email (IBM server dual xeon 3.2GHz, 3GB RAM, Server 2003 R2 SP1) has had a couple of issues lately. two weeks ago (October 16) exchange slowed to a crawl and users were getting constant warning messages that Outlook was trying to communicate with the Exchange server. the problem seemed to be resolved with the next update but the same thing happened again today and again fixed with an update. Thats all ok now, but I noticed last time there was a problem, that xmon was causing the store.exe service to use a constant 25% processor time. restarting just the info store made no difference, but after applying the nod32 update and restarting xmon and the info store, this dropped down to a normal pattern varying between 0 and 10%. I noticed a couple of days later that the info store was back to sitting on 25% CPU load again (but all seemed to be functioning correctly) and it stayed at 25% until the problem we had this morning. Turning off xmon and restarting the info store dropped the usage back to minimal again, and restarting xmon and the info store after the update hasn't caused any increase in CPU load yet. The other 4 exchange servers don't seem to have this issue of high load but they also host fewer mailboxes (80 mailboxes on the problem server and 20-50 on each of the others).
Is this normal behaviour for xmon?
Thanks in advance
Geoff