Problem with JMS in a Cluster

Question

In summary I am having a problem with my application when it is running on the server that does not contain the JMS.
          Setup:
          2 machines:- Server 1 with the Admin Server and a Managed Server with JMS and a Distributed Queue. Second machine (Server 2) with a managed server. The two managed servers are in a Cluster.
          The connection factory has xa enabled.
          The queue is a distributed queue, with one member queue - on server 1.
          Scenario 1 (works):
          Deploy my application on Server 1 only
          Scenario 2 (works):
          Deploy my application on Server 1 and Server 2
          When the application puts messages on the JMS queue, the messages are processed round robin by the MDB on both Server 1 and Server 2 - as expected.
          Scenario 3 - Does not work
          Deploy my application on Server 2 only
          The application successfully sends a message to the queue - I can see it in queue through the console.
          However the MDB never processes the message. On the queue, I can see 0 consumers.
          Essentially the MDB appears to deploy correctly from the server log but never appears as a consumer on the queue.
          I know the above information is very brief, however I can provide more configuration details and detailed logging if required.

Answer 1

On a further look through the logs, I have found the following Warning message which may point to the reason why my MDB is not receiving messages from JMS:
          <25-Apr-2005 17:26:01 o'clock IST> <Warning> <EJB> <BEA-010220> <The jms destination 'AsyncMessageQueue' is a distributed destination and it has no physical destination(s) on the current weblogic server. As per distributed destination co-location rules, no pool was creted for the MDB 'AsyncMessage(Application: m3-j2ee_Weblogic21apr_2, EJBComponent: ejb_framework.jar)' on this weblogic server. Hence the MDB 'AsyncMessage(Application: m3-j2ee_Weblogic21apr_2, EJBComponent: ejb_framework.jar)' cannot receive any messages on this server.>
          I have created a Destination on the JMS Server ("Replicate JNDI Name In Cluster" is set), and I have created a Distributed Destination, which has as its member the Destination associated with the JMS Server.
          If the JMS is not on the same server as the deployed application, how do I get the MDB to connect to the physical destination?
          Do I always need a Physical Destination on the the same server as my deployed application? If so, how do I create a Physical Destination on the server that does not have the JMS?
          Any help appreciated.