JSESSIONID Persistance based on jsessionid in URL

You always attach One Connect right? Please check https://support.f5.com/csp/article/K82540512 and try with one connect and if there are issues with LB::detach as described. You can also test with hash persistence based on the JSSESSION https://support.f5.com/csp/article/K11362 . Also if the servers are configuring the cookie (you use hash cookie so Ithink they add a cookie) is easier to use that cookie than you adding the cookie on the F5 device. You may also check for TCL errors in the LTM log as I think you have taken the example from https://support.f5.com/csp/article/K7392 / https://devcentral.f5.com/s/articles/weblogic-jsessionid-persistence