<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.2">
<TITLE>Sequencing of event queue</TITLE>
</HEAD>
<BODY>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Tahoma">Hello workflowers! The question that I put to you today is regarding the workings of the event queue.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Tahoma">We have seen in our Production environment that if the event queue has filled up and is not being cleared completely by every job run but in fact keeps on building up through time</FONT><FONT SIZE=2 FACE="Tahoma"> (as a result of a batch job that triggers many workflows)</FONT><FONT SIZE=2 FACE="Tahoma">, the event delivery job will deliver the most recent events instead of the oldest events.</FONT> <FONT SIZE=2 FACE="Tahoma"> </FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Tahoma">In other words, the event queue is behaving as a LIFO</FONT><FONT SIZE=2 FACE="Tahoma"> (Last In First Out)</FONT><FONT SIZE=2 FACE="Tahoma"> queue instead of a FIFO</FONT> <FONT SIZE=2 FACE="Tahoma">(First In First Out)</FONT> <FONT SIZE=2 FACE="Tahoma">queue. It was my understanding that the queue should be FIFO.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Tahoma">Any comments? Anybody else seen this happening?</FONT> <FONT SIZE=2 FACE="Tahoma"> Any solutions????</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Tahoma">The sequencing is extremely important to some workflows that we have</FONT> <FONT SIZE=2 FACE="Tahoma">and</FONT><FONT SIZE=2 FACE="Tahoma"></FONT> <FONT SIZE=2 FACE="Tahoma">we</FONT><FONT SIZE=2 FACE="Tahoma">'</FONT><FONT SIZE=2 FACE="Tahoma">d like to see the queue behave as a FIFO queue.</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Tahoma">Cheers</FONT></P>
<P ALIGN=LEFT><FONT SIZE=2 FACE="Tahoma">David</FONT></P>
<CODE><FONT SIZE=3><BR>
<BR>
* ** *** ** * ** *** ** * ** *** ** * <BR>
This email and any files transmitted with it are confidential and <BR>
intended solely for the use of the individual or entity to whom they <BR>
are addressed. <BR>
Any views or opinions presented are solely those of the author, and do not necessarily <BR>
represent those of ESB. <BR>
If you have received this email in error please notify the sender. <BR>
<BR>
Although ESB scans e-mail and attachments for viruses, it does not guarantee <BR>
that either are virus-free and accepts no liability for any damage sustained <BR>
as a result of viruses. <BR>
<BR>
* ** *** ** * ** *** ** * ** *** ** *<BR>
</FONT></CODE>
</BODY>
</HTML>