Robert Davis (6/20/2012)
You are less likely to have a name resolution problem if you use the fully qualified domain name of the servers. Name resolution is probably the root cause of the issue. Then you encountered a "poisoned queue" issue. Mirroring is built on top of the service broker engine, and too many consecutive errors will cause the queue behind the endpoint to shut down (the endpoint is still running, but the queue behind it is not).cherish.j.wang showed you how to get the queue to start up again, but the root cause may still need to be addressed.
Robert is correctly. I don't the root cause yet. I have came across this issue of mirroring many time and fixed it via restart endpoint already.;-)