Odd behaviour when pooling to a Tomcat server

Hi Hollio (or anyone for that matter!),

 

 

We still haven't nutted this out yet. The developers did some code changes on the Tomcat App side they thought may have causing the issue, but no go. There is one other difference the developers picked up which they think could be the issue. On the working environment when the BigIp accesses the tomcat pool a session variable called BigipServer is created and it has a Path of /online , /online being the text we look for in the URI to direct the traffic to the Tomcat server. On the environment that does not work the cookie to the Tomcat pool is created but it's Path is set to /. Is there anyway to set the path, or any ideas on why the path's would be different? I'm not doing anything explicitly to create these pool cookies, I assume it's a function of the BigIp.

 

 

tia

 

 

Craig