Forward Delay not working

Question

I have a distributed queue, whose subdeployments points to two JMS Servers each having there own persistent DB store. Now i have configured forward delay of 5 (implying 5 seconds) on the Distributed Queue. So essentially if there are no consumers for a queue for 5 seconds the messages should be forwarded to other member of the distributed queue but the same is not happeneing, the messages never get forwarded to other member in the distributed queue? What could be the problem?

Answer 1

I have already checked the JNDI tree and those show the distributed members correctly.
As you said as of weblogic 9.2 its not queue forward is not encoraged then how come MDBs are able to listen from both queue members.
Eg: Say you have two queue emmebr but when you start your servers only one is accessible so all consumers will listen to queue member QA availbel on jms server JA having database persistent store DA, the other queue member QB available on JMS server JB having database persistent store DB will not be listened to even after the seconds managed server on whch JB is deployed comes back?Yes - MDBs handle all cases automatically.
When an MDB runs on a different cluster/server than its source distributed queue, it automatically creates at least one active consumer on each distributed queue member.
When an MDB is targeted to the same cluster as its source distributed queue, it automatically creates a deployment for each queue member, or, in very limited situations, you may want to configure a behavior that causes each local deployment to connect to every queue member.
The MDB code automatically dynamically handles all cases of changes in member availability such as shutdown, start, new configured members, deleted members, and the migration of members from server to server.
I am not sure if you have can two JMS servers using the same DB Store?No. No two JMS servers can share a DB store unless the JMS servers and DB store all share the same target (and therefore all run on the same WebLogic Server). Even then, the two JMS servers will not manipulate or expose each-other's messages -- they will only expose their own messages.