matchclass, uri routing, and cookie persist & snat irule

So some other thoughts I had on the above:

 

 

in each clause I'm assuming that the LTM will automatically try to persist off of the various SESSIONID cookies listed above, assuming they are indeed present. If they exist we should be good, but if they don't (like on an initial visit to the site) will the LTM iRule err out and stop processing or just ignore the persist command (as I'd hope it might)?

 

 

This assumption continues with the ELSE clause where, if any request comes in which does not match one of the aforementioned URIs, the LTM should try to persist it using the named cookie (UMPSESSIONID) and then send it to the appropriate pool, whether as a sticky session or a new session.

 

 

As a side note, I got some of the syntax above from another iRule on this site which outlined utilizing the JSESSIONID cookies for J2EE app server persistence:

 

 

http://devcentral.f5.com/wiki/iRules.Weblogic_JSessionID_Persistence.ashx

 

 

In that iRule, I noticed that there was also an HTTP_RESPONSE section listed. Just wondering if I'd need an HTTP_RESPONSE clause in this iRule for it to properly work, based on the other tech page link I've listed above?

 

 

And also on that page is a note from Aaron (hoolio), indicating that we need to use OneConnect for that iRule to work? We've been using that persistence iRule for some time now and don't have OneConnect enabled for that VS. Could this be causing odd connection issues, and should I look at enabling it for this rule too?

 

 

Thanks in advance!

 

B