Hello Bonehead,
Not knowing the size of your implementation outside of a pretty serious event
storm, I would say generally speaking that when you see that problem on the
MS, it means trouble communicating with / inserting into the database. Could
be connectivity, could be latency in the SQL due to disk or other factors.
If your server gets backed up for long enough, you'll see the problem crop
up on the agents as they are forced to queue data. If the problem were only
on the agents, I would say connectivity is often the cause, through DNS or
network connectivity issues
I'd start with the MOM server, check DB performance and connectivity. How
many disks in the array where Onepoint is hosted? Is Onepoint on a dedicated
database server?
Also, how to check for an event storm
http://support.microsoft.com/?id=923103
Regards,
Pete Zerger, MCSE(Messaging), MVP - MOM
URL:http://www.momresources.org
BLOG: http://www.it-jedi.net/
> I am having problems with MOM Server and Agent queues. There are
> event ID's 22061/22062 for Agent data processing and 21268/21269 for
> Server queues.
> (Two-Tier MOM 2005 SP1 setup)
> Event Information:
> 21268 - The Server incoming queue data submission has been blocked
> 21269 - The Server incoming queue now has sufficient space or is
> available
> to process new data.
> 22061 - The Agent outgoing data processing has been blocked.
> 22062 - The Agent outgoing data processing has successfully resumed
> after
> being blocked.
> I have doubled the Global settings for the queues with no effect. Has
> anyone encountered this same problem?
> Thanks,
> - JF