Difference between 'JMS Queue Message' activity and 'Wait for JMS Queue Message' activity

Wait for JMS Queue Message activity starts listening for messages from the time the BusinessWorks engine starts.
Get JMS Queue Message activity starts listening for incoming messages on the specified queue from the time the activity is triggered.

This can test by developing two simple example processes.i.e

First create a queue and place some pending messages in queue.

build a process_defention1 with one Wait for JMS Queue Message activity and configure it with queue name.
build a process_defention2 with one Get JMS Queue Message activity and configure it with queue name.

If we just start process_defention1 ,then the pending message count = 0. (No need to trigger Wait for JMS Queue Message activity)
If we just start process_defention2 ,then the pending messages count = not zero. it becomes zero when the Get JMS Queue Message activity triggered.

● Get JMS Queue Message activity can receive only one message from the specified queue at a time, when the Message Selector is not used.
Get JMS Queue Message activity once triggered, then this  can either gets a message from the specified destination queue name before timeout and proceeds or it throws a timeout error and exits.

Wait for JMS Queue Message activity is non starter activity which behaves like queue reciever (starter activity) 

  © Blogger templates The Professional Template by Ourblogtemplates.com 2008

Back to TOP