Weblogic.jms.common.jmsexception error binding connection factory
In this blog post I will demonstrate an error handling mechanism which can be used to achieve guaranteed delivery of messages in a specific order.To implement this I have used Oracle SOA Suite 11g, BPEL 2.0.The selector which is set when producing is shown in the text near the arrow.The number between brackets indicates the order of an example flow in which an error occurs in the problem Service.50% of the time this process fails and throws a SOAP exception.JMSProject is used to produce a message to the JMSTopic.A single JMS topic is used and JMS message selectors based on custom JMS headers are used by clients.
It then produces the same message again with selector 'A' The above picture shows how the processes are related. An arrow from the Topic to a process (the other boxes are the processes) indicates the process consumes messages.
Subscription sharing policy allows several clients with the same Client Id to register for messages. Multiple hosts can be registered to the same topic this way using the same connection factory.