How do you get distributed destinations to work ?

Question

          Hi all,
          I'm trying to getting to work Distributed JMS Destinations. But
          still without success. This is the sitation:
          Node1---->JMS Server1------>Queue1 [Distributed destination1]
          Node2---->JMS Server2------>Queue2 [Distributed destination1]
          I have a cluster with 2 Nodes.
          I have created 2 JMS Servers each one targetted on one Node.
          Then I have created 2 Queues and added them to a Distributed Destination as member.
          Now I start the QueueSender (pointing to the Distributed Destination's JNDI)
          I start 2 QueueReceivers (pointing to the JNDI of the 2 Queues).
          The problem is that when one of the two nodes, let's say Node1, fails
          messages aren't dispatched to the JMS Server2.
          So I wonder: Is it possible that if one of the 2 JMS Server fails
          the message is redirected to the other JMS Server ?
          Thanks a lot
          Francesco
          

Answer 1

Receivers only load-balance once - when
          they are first created. The JMS Performance
          Guide explores the implications of this.
          Keep in mind that the distributed destination
          feature was optimized for the case where
          receivers (generally MDBs) run on the same
          servers as the distributed destination
          instances, which simply load balances each
          receiver to its local destination instance.
          Otherwise, if the receivers
          are not co-located with distributed destination
          instances, load-balancing
          configuration requires special care to prevent
          physical destinations from not getting served
          by receivers.
          One solution for the latter problem, as you
          already wrote below, is to receive directly from the
          physical destinations - which removes the
          load balancing decision all-together.
          Francesco wrote:
          > Hi,
          > thanks a lot for your clean answers.
          > Ps has anybody got an answer about my last question (That is, should I lookup
          > the JNDI
          > of the single Queue or of the Distributed Destination in order to get distributed
          > destination to work ?)
          > Thanks a lot
          > Francesco
          >
          > Tom Barnes <[email protected].bea.com>
          > wrote:
          >
          >>It is normal for a sender to get an exception
          >>when its connection's host server goes down.
          >>The client connection's host server does
          >>not change for the life of the connection,
          >>and does not automatically fail-over.
          >>Even when the client's connection host stays up
          >>but the JMSServer hosting the current
          >>distributed destination instance goes down, the sender
          >>may still get an exception. Such an exception
          >>can indicate that there is ambiguity as to
          >>whether or not the JMS server received the
          >>message from the send().
          >>
          >>The standard way to handle
          >>such exceptions is to re-establish the connection,
          >>session, and producer on the client (usually
          >>using the exact same code that initialized
          >>these resources to start with.)
          >>
          >>In addition, it is highly recommended
          >>for the client to register exception listeners
          >>on both the connection and on the WLSession.
          >>
          >>Tom
          >>
          >>Francesco wrote:
          >>
          >>
          >>>"Barry Myles" <[email protected]> wrote:
          >>>
          >>>
          >>>>Hi Francesco
          >>>>
          >>>>Try creating a connection factory that has Load balanced ticked and
          >>
          >>server
          >>
          >>>>affinity
          >>>>unticked
          >>>>
          >>>>now make sure that the distributed destinations load balancing property
          >>>>is set
          >>>>to Round Robin
          >>>>
          >>>>
          >>>>
          >>>>>I start 2 QueueReceivers (pointing to the JNDI of the 2 Queues).
          >>>>
          >>>>Also when the QueueRecievers are running do you see one consumer attached
          >>>>to each
          >>>>physical queue?
          >>>>
          >>>>HTH
          >>>>
          >>>>
          >>>>"Francesco" <[email protected]> wrote:
          >>>>
          >>>>
          >>>>>Hi all,
          >>>>>I'm trying to getting to work Distributed JMS Destinations. But
          >>>>>still without success. This is the sitation:
          >>>>>
          >>>>>Node1---->JMS Server1------>Queue1 [Distributed destination1]
          >>>>>Node2---->JMS Server2------>Queue2 [Distributed destination1]
          >>>>>
          >>>>>I have a cluster with 2 Nodes.
          >>>>>I have created 2 JMS Servers each one targetted on one Node.
          >>>>>Then I have created 2 Queues and added them to a Distributed Destination
          >>>>>as member.
          >>>>>
          >>>>>Now I start the QueueSender (pointing to the Distributed Destination's
          >>>>>JNDI)
          >>>>>I start 2 QueueReceivers (pointing to the JNDI of the 2 Queues).
          >>>>>
          >>>>>The problem is that when one of the two nodes, let's say Node1, fails
          >>>>>messages aren't dispatched to the JMS Server2.
          >>>>>
          >>>>>So I wonder: Is it possible that if one of the 2 JMS Server fails
          >>>>>the message is redirected to the other JMS Server ?
          >>>>>Thanks a lot
          >>>>>Francesco
          >>>>
          >>>Hi Barry,
          >>>I have tried to modify the connection factory as you said but
          >>>I'm still stuck. Basically when I shut down one of the two Nodes, the
          >>
          >>Sender
          >>
          >>>receives an exception "IllegalStateException: Producer is closed".
          >>>
          >>>Could you tell me if it's basically correct that :
          >>>
          >>>Sender----->looks up the Distributed Queue
          >>>Receivers---->look up the single Queues (which belong to the Distr.
          >>
          >>Queue)
          >>
          >>>Thanks again
          >>>Francesco
          >>
          >