WebLogic Application Server Usage Notes
The following technical considerations apply when you use webMethods Broker as a JMS provider with the WebLogic Application Server:
When you use
webMethods Broker as a JMS provider, the connection factories that generate and bind into the JNDI provider implement the
XATopicConnectionFactory and
XAQueueConnectionFactory interfaces. These factories provide support for the Java Transaction API (JTA). The WebLogic Application Server will create actual XA connections and XA sessions from the connection factories only if the trans-attribute is set to "Required" in the ejb-jar.xml deployment descriptor file.
A WebLogic MDB listener with a message selector does not receive messages if the publisher and subscriber are sharing the same
connectionId.
WebLogic Application Server sets the noLocal flag to True if filters are enabled. Because of this, when you use webMethods Broker as a JMS provider, it does not recognize messages if the publisher and subscriber are sharing the same connectionId. To work around this limitation, ensure that the connectionIds for publishers and subscribers are different in the objects that you bind to the JNDI provider.