JMS sub-deployment targeted to cluster

Question

Hello,
I have read at the Oracle documentation that we can use a sub-deployment within a JMS module targeted only to a single JMS Server. But I have an application that create JMS resources with deploy descriptors (Application modules) and target the sub-deployment to a cluster with two machines, each machine has a JMSServer. It seems to work (I see them on the JNDI tree on both machines). This is the jms.xml:
Do you also use sub-deployment targeted to a cluster or I shouldn't? Thank you in advance ;)
I am using webLogic version 10.3.4.0
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-jms xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-jms"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-jms http://xmlns.oracle.com/weblogic/weblogic-jms/1.1/weblogic-jms.xsd">
     <wls:quota name="InboundMessageQuota">
          <wls:bytes-maximum>1000000</wls:bytes-maximum>
          <wls:messages-maximum>10000</wls:messages-maximum>
     </wls:quota>
     <!-- Factories -->
     <wls:connection-factory name="InboundMessageConnectionFactory">
          <wls:sub-deployment-name>InboundMessage</wls:sub-deployment-name>
          <wls:jndi-name>jms.InboundMessageConnectionFactory</wls:jndi-name>
          <wls:security-params>
               <wls:attach-jmsx-user-id>false</wls:attach-jmsx-user-id>
          </wls:security-params>
     </wls:connection-factory>
     <!-- Queue's -->
     <wls:uniform-distributed-queue name="InboundMessageQueue">
          <wls:sub-deployment-name>InboundMessage</wls:sub-deployment-name>
<wls:delivery-params-overrides>
<wls:delivery-mode>Non-Persistent</wls:delivery-mode>
</wls:delivery-params-overrides>
<wls:delivery-failure-params>
<wls:redelivery-limit>0</wls:redelivery-limit>
</wls:delivery-failure-params>
          <wls:jndi-name>jms.InboundMessageQueue</wls:jndi-name>
     </wls:uniform-distributed-queue>
</wls:weblogic-jms>

Answer 1

Technically, cluster targeting a distributed destination is supported, and it'll work as long as your can be absolutely assured that the cluster will never host additional JMS servers - perhaps from future projects, or due to integrating third party products. Otherwise, your distributed destinations will end up creating instances on JMS servers where they don't belong - a common mistake that can be tough to diagnose and untangle. I highly recommend staying with the best practice of using a subdeployment that references exactly the intended JMS servers. Note that a subdeployment can reference more than one JMS server.
See [url  http://download.oracle.com/docs/cd/E17904_01/web.1111/e13738/best_practice.htm#JMSAD455] WL JMS Configuration Best Practices
Hope this helps,
Tom