public SyncMessageConsumerUsingReceieve(string EMSQueueName, int NoOfSessions, int Timeout)
{
for (int i = 0; i < NoOfSessions; i++)
{
QueueSession session = Messaging.EMS.Connection.EMSQueueConnection.connection.CreateQueueSession(false, QueueSession.CLIENT_ACKNOWLEDGE);
Queue queue = session.CreateQueue(EMSQueueName);
QueueReceiver receiver = session.CreateReceiver(queue);
Message ReceivedMessage;
Thread t1 = new Thread(() =>
{
Thread.CurrentThread.Name = "Explicit Thread for Session-" + session.SessID;
if ((ReceivedMessage = receiver.Receive(Timeout)) != null)
{
this.ReceiveAndProcessMessage(ReceivedMessage);
/* A Receive call that returns as and when message is received or when it timesout . Achieves concurrent
* consumption thats one-time i.e as soon as processing is completed ,so is the thread.
* Sync. consumer will be required when a flow triggered by some non-ems mechanism/protocol needs to
* fetch messages off EMS . Most likely, NoOfSessions=1 and Timeout=<int> in this sceanrio.
* Main thread does not wait for the threads to finish , however multiple receivers/consumers so created
* will be destroyed all at once and not one-by-one.
* You dont want it to put in loop , unlike in the other constructor , because there is not much use
* repeating something that did not fetch anything in first place and had to time out.Rather
* this mechanism is better suited where possibilty of message arrival is rather low or producer is sluggish.
*/
}
}
);
t1.Start();
}
}
//protected String EMSQueueName;
//protected int NoOfSessions;
public SyncMessageConsumerUsingReceieve(string EMSQueueName, int NoOfSessions, Boolean KeepAlive)
{
for (int i = 0; i < NoOfSessions; i++)
{
QueueSession session = Messaging.EMS.Connection.EMSQueueConnection.connection.CreateQueueSession(false, QueueSession.CLIENT_ACKNOWLEDGE);
Queue queue = session.CreateQueue(EMSQueueName);
QueueReceiver receiver = session.CreateReceiver(queue);
Message ReceivedMessage;
Thread t1 = new Thread(() =>
{
Thread.CurrentThread.Name = "Explicit Thread for Session-" + session.SessID;
while ((ReceivedMessage = receiver.Receive()) != null)
{
this.ReceiveAndProcessMessage(ReceivedMessage);
if (!KeepAlive)
{
break; /* With NoOfSessions=1 and KeepAlive=false , achieves effect of a single Receive call that
* returns as and when message is received. NoOfSessions > 1 and KeepAlive=false achieves concurrent
* consumption thats one-time i.e as soon as processing is completed ,so is the thread.
* Sync. consumer will be required when a flow triggered by some non-ems mechanism/protocol needs to
* fetch messages off EMS . Most likely, NoOfSessions=1 and KeepAlive=false in this sceanrio.
* Main thread does not wait for the threads to finish , however multiple receivers/consumers so created
* will be destroyed all at once and not one-by-one.
*/
}
}
}
);
t1.Start();
}
}