Sequencing of event queue

[Michael Pokraka]

Glad we could be of assistance :-)

I have encountered this before and found no fix at the time, it's nice to know
that it has been addressed, so thanks for the info. 

Cheers
Mike

--- "Yung. David" <David.Yung at esb.ie> wrote:

> I just found SAP note 817848 (released 13 days ago!!) which refers to this
> very thing...  Had to call on a german friend to translate though 'cause
> it's still not in English...
> 
> Cheers
> 
> David
> 
> 
> 		-----Original Message-----
> 		From: Yung. David 
> 		Sent: 23 February 2005 09:17
> 		To: 'SAP-WUG at mit.edu'
> 		Subject: Sequencing of event queue
> 
> 		Hello workflowers!  The question that I put to you today is
> regarding the workings of the event queue.
> 
> 		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 (as a result of a batch job that
> triggers many workflows), the event delivery job will deliver the most
> recent events instead of the oldest events.  
> 
> 		In other words, the event queue is behaving as a LIFO (Last
> In First Out) queue instead of a FIFO (First In First Out) queue.  It was my
> understanding that the queue should be FIFO.
> 
> 		Any comments?  Anybody else seen this happening?  Any
> solutions????
> 
> 		The sequencing is extremely important to some workflows that
> we have and we'd like to see the queue behave as a FIFO queue.
> 
> 		Cheers
> 
> 		David
> 
> 
> * ** *** ** * ** *** ** * ** *** ** * 
> This email and any files transmitted with it are confidential and 
> intended solely for the use of the individual or entity to whom they 
> are addressed. 
> Any views or opinions presented are solely those of the author, and do not
> necessarily 
> represent those of ESB. 
> If you have received this email in error please notify the sender. 
>  
> Although ESB scans e-mail and attachments for viruses, it does not guarantee 
> that either are virus-free and accepts no liability for any damage sustained 
> as a result of viruses. 
>  
> * ** *** ** * ** *** ** * ** *** ** *
> 
> > _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>