Hello,
The problem I was having regarding re-enable a queue was because it was in another database. I am guessing it did that because the contract and Queues have the same name. I double checked and nothing pointed to that database. I fixed it because I can re-enable the queue in the other database and it is fixed. My question is why did this happen? The other issue I am still having is regarding why the queue got disabled to begin with. I understand that it was because of positioning but do not understand how or why and how to provent it from being disabled.
Thanks,
Scott Allison...
You can have a contract and a queue inside one database with the same name without any conflict. You queue may be getting disabled due to poisoned message detection. You can read about this in Books Online. In short, if you receive from a queue and rollback 5 times consecutively, we detect that the queue probably has a bad message and disable it.
Rushi
No comments:
Post a Comment