I have a local queue which is set to trigger on EVERY message. This works fine until the queue manager is shut down and restarted. In this case if there are messages in the queue on restart a single trigger message is generated, instead of one per message. Whilst this follows the rules specified in the administration manual, it leaves messages not being processed. My solution was to turn the trigger property on and off for each message in the queue, but I am sure there must be a better way?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Generating trigger messages after restart
- Thread starter VinceH
- Start date
MiddlewareOnline
IS-IT--Management
Well, it is NOT a good idea to have trigger (EVERY). The application being triggered should get with wait. This way all the messages that arrived when the triggered was fired plus that arrived during the processing would be picked up.
If you can explain why you want to do on/off of trigger may be we can suggest you another option.
MiddlewareOnline.COM IBM MQ Series Certified Consultants
A SARVAM PORTAL
If you can explain why you want to do on/off of trigger may be we can suggest you another option.
MiddlewareOnline.COM IBM MQ Series Certified Consultants
A SARVAM PORTAL
- Thread starter
- #3
The application being called can only handle one message at a time, hense the need for Every. Turning the trigger property off and on generates a new trigger message and therefore causes another message to be processed, this needs to be repeated for every message in the data queue.
- Status
Similar threads
- Locked
- Question