OneConnect Transformations reuse from same source IP address and port number?

Keepalive connections aren't "recycled" per se, they are kept open & re-used: The connection is maintained open unless idle timeout or max requests is reached. Once the idle timeout or max requests force the server to close the connection, normal close mechanics apply & connection may go into TIME-WAIT for 2MSL, preventing connections to the same IP:port tuple. (YMMV depending on any stack optimizations for faster socket re-use.)

 

 

OneConnect transforms just change non-keepalive connection requests on the client side to keepalive connections on the serverside. So with OneConnect transformations enabled but OneConnect not, I'm fairly certain that the net effect is really null, or perhaps even negative for your servers: If a client initiates a non-keepalive connection, the client will never re-use that client-side connection, but the server may hold that connection open until the client side connection closes or the default serverside keeplive timeout expires.

 

 

Even with OneConnect enabled, access by the same clientside IP:port are not guaranteed to use the same serverside connection -- that connection may already be in use by another clientside flow. Setting the OneConnect mask to host (32 bit) is the best way to maximize that possibility.

 

 

HTH

 

/deb