Jump to content

infinite messages to $sys.undelivered and main Queue when useing JMS_TIBCO_PRESERVE_UNDELIVERED


Kamilia Jaber

Recommended Posts

I'm using Tibco BW6 with Tibco EMS, and I'm trying to build a failover mechanism for my application as follows:

1- Use JMSRecieverMessage to pull a message from my Queue, and handle it, It should be checked 3 times, if failed, I should send it to $sys.undelivered Queue.

2- I have configured my queues.conf and setmaxRedelivery=2 .

3- I have used a JMSSendMessage to set a new property withJMS_TIBCO_PRESERVE_UNDELIVERED = 'true'

* I have attached all images for my configurations.

When I run the application to handle one message on the queue, it goes on an infinite loop by pulling messages and pushing messages on both the original (source) Queue and$sys.undelivered Queue.

However, when I removedJMSSendMessage, it works fine with the count, pull the message and consume it 3 times, then remove it from the queue.

 

Please advise

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...