This content has been marked as final. Show 2 replies
The issue as indicated by the error appears due to duplete durable subscription. You might need to review this design or leave it as such.
Even if Tibco allowed duplicate durable subscription (which violates jms spec), then each of your soa managed server will get a copy of the message resulting in duplicate messages which might do more harm for you. Current setup allows only one subscriber (a race condition whichever managed server connecting first) means you will get only one copy of the message , though all the load ends up in one managed server.
You can slightly modify the design, where you can have a soa router composite( or can use weblogic messaging bridge) with an in and out jms adapter which gets the message off the tibco topic and forwards to a weblogic distributed queue with load balancing turned on. You can then have your heavy composite consuming messages off the distributed queue. Even though soa router composite load will be only on one managed server at any time it might be very little as it doesnt do anything much other than routing. The load on the original heavy composite will be load balanced.