T3 Weblogics Protocol

A couple comments/observations and a question about your agile 'java' service.

 

 

I think your java service works because the listening port matches the port on all members of the weblogic service pool. that is, the weblogic client writes the port in the payload and it must match (there is another article on this--" replace port by other in TCP payload" dated 12/14/2010 at 02:27PM.

 

 

we find that to be the case here too. if the F5 service port is different from the port in the members of the pool, the code will fail.

 

 

now my question.

 

 

the virtual server for the java does not have an persistence set on it. How is it persisting to the same pool member? we also found that the client would not work if we didn't provide persistence (or if the pool only had one member active). we are using source IP since it is a fast layer 4 type.

 

 

note that we run the web service as standard port 80 / 443 with cookie persistence on the same IP.. Similar to what you listed in 1 except yours also used port 7001 on a different IP.

 

 

thanks.