Forum Discussion

Hamish's avatar
Hamish
Icon for Cirrocumulus rankCirrocumulus
May 18, 2010

iRule events firing out of order?

Is it SUPPOSED to be posisble for events to fire out of order?   . I have a 10.1.0 6900 that's running an iRule to measure LDAP searchtimes. As part of it, it sets up a few variables in SERVER_CONN...
application delivery
dev
devops
iRules
Hamish's avatar
Hamish
Icon for Cirrocumulus rankCirrocumulus
May 18, 2010
Hmm... Not my iRule, so let me look..

 

 

Yes, a TCP::collect is being used in CLIENT_DATA, but that should simply collect data for a CLEINT_DATA event.

 

 

The SERVER_CONNECTED should run before SERVER_DATA... I dont' see how we could get SERVER_DATA even called without a TCP::collect in SERVER_CONNECTED first... But if that were true, then I also don't see why a variable set in SERVER_CONNECTED is sometimes undefined in SERVER_DATA... (Only about 4% of the time, but it does happen).

 

 

Hmm... Order of processing... Is it possible that SERVER_DATA is being called AFTER SERVER_CONNECTED but BEFORE the SERVER_CONNECTED event has finished? Can TCP::collect cause an event to be 'paused' and pre-empted by the _DATA event?

 

 

Hm... Down the bottom of the TCP::collect wiki page... Says TCP::collect implicitly holds the accepted event... Does that mean what I think it means? Although Sparks example back from 2008 seems to indicate that it isn't http://devcentral.f5.com/Forums/tabid/1082223/asg/50/showtab/groupforums/aff/5/aft/24911/afv/topic/Default.aspx (Because he sets variables after his collect too).

 

 

Let me try moving some code around and put the TCP::collect at the end of the SERVER_CONNECTED event...

 

 

H