Hi, i know that this is totally against the idea of mdbs, but my mdb will update memcache so if messages come to fast the AS will create more than one mdb and they will try to update memcache simultaneously and this will blow. If i make my mdb singleton this will not happen, the mdb will update the memcache sequentially(i think). And although it is too frequently it will be sequentially, so i think it will work.
Hi I will deploy the mdb on a clustered env. It will listen to clustered queue. Is there any way to do the mdb to be singleton for the whole cluster?
