JSESSIONID Persistence

[wfesouza]

WARN    22/Oct/2012:09:30:26 -0400    WARN    Rule url_rewriting_response: Line 8: Regular expression ".;JSESSIONID=().", subject length 1213180: Performance warning: took: 12.850150 seconds    guarani05<br>WARN    22/Oct/2012:09:30:26 -0400    WARN    Rule url_rewriting_response: Line 8: Regular expression ".;JSESSIONID=().", subject length 1213180: Performance warning: more than 5% (1000000) of trafficscript!regex_match_limit    guarani05
WARN    22/Oct/2012:09:30:26 -0400    WARN    Rule url_rewriting_response: TrafficScript rule has buffered over 1048576 bytes of response data    guarani05
WARN    22/Oct/2012:09:28:51 -0400    WARN    Rule url_rewriting_response: Line 8: Regular expression ".;JSESSIONID=().", subject length 1180030: Performance warning: took: 12.822114 seconds    guarani05<br>WARN    22/Oct/2012:09:28:51 -0400    WARN    Rule url_rewriting_response: Line 8: Regular expression ".;JSESSIONID=().", subject length 1180030: Performance warning: more than 5% (1000000) of trafficscript!regex_match_limit

[fmemon]

Hi wfesouza,

Would you be able to post the TrafficScipt code you used?

Thanks,

Faisal

[wfesouza]

The script used are described in the attached documentation.

[fmemon]

Hi wfesouza,

Sorry for the late reply.  Are you using the code snippet on page 7?  That does a regex match against the URL.  The error message indicates the string you are passing to string.regexmatch() is over 1 MB in length.  Are your URLs that long?

Thanks,

Faisal

[wfesouza]

Are you using the code snippet on page 7?

R. Yes

The error message indicates the string you are passing to string.regexmatch() is over 1 MB in length.  Are your URLs that long?

R. yes we have great URLs

The message is "warning", it is a problem for the persistence in stingray?

[fmemon]

Hi wfesouza,

Sorry for the late reply.  It should still work ok as its just a warning.  If you increase the values of trafficscript!regex_match_limit and trafficscript!regex_match_warn_perc under System -> Global Settings -> Other Settings that should help suppress the warning messages.

Thanks,

Faisal

[owen]

Hi Wagner,

I can't tell which bit of documentation you are referring to, but we have published several WebLogic/JBoss/Oracle deployment guides that include a rule named 'url_rewriting_response' which searches for a JSESSIONID.

In some cases, these rules will search for a JSESSIONID in the body of a response, and this may be what is triggering the error you have seen.

The good news is that since writing the deployment guides, we added a new session persistence class that handles JSESSIONID session persistence much more capably and avoids the need to inspect the response.  You could either check out the documentation for the JSESSIONID persistence class, or let us know what rule/deployment guide you are working from and we'll update you.

Thank you

Owen