Since implementing DUCS 1.2.1 on our clustered mail environment, our servers having been locking up frequently due to various mail files getting corrupted, and locked semaphores not releasing. Although we are having IBM look into this, these sorts of problems did not occur until DUCS came into the picture.
We have found there is no relationship to IMAP, POP3, or HTTP as a result of diagnosing the problem (despite the fact that there was a previous documented issue on R5 servers related to IMAP). If DUCS is not the direct cause, it is most definitely the catalyst yielding the problems we are experiencing.
I will update this post later on status, but for anyone planning to implement this product, you may want to think twice until these sorts of problems are corrected. I don’t believe the issues we are experienced are corrected in 1.2.2.
We may create an adjacent domain and setup voicemail-only mail files, and re-do the entire implementation, to try to isolate the Unity/DUCS processes, and separate it from primary email files altogether.