I am working with a JMS application which requires durable subscription as we cant afford to lose any messages. Also the same message is consumed by multiple MDBs (Typical Topic paradigm). It is also essential that the same message is not processed by an MDB more than once (Can not handle duplicates). We are currently working fine on a single machine weblogic 8.1 server with absolutely no problems.
How do i get this on to a clusterd environment with multiple weblogic instances ? I tried to use a distributed topic , but my mdbs refuse to deploy to more than one server - throwing an exception client id already in use.
Any ideas on where i am going wrong ? Weblogic suggested getting their technical team to review the design. We are not keen on this. Is it a design problem or an inherent JMS issue ? Any ideas ?