we want to change the default connection timeout setting via the CWP io.outConnectTimeout.
But once we set this CWP it seems to not work directly. If I check the "Route via HTTP"-assertion of existing policies it still shows the old value. I thought CWP are active immediately? Or do we have to restart any processes? Or is this maybe depending on the CWP itself?
Any idea to get this fixed would be very helpful!
Good afternoon. The cluster wide properties that affect settings on the connection tab of the HTTP Routing assertion will not modify the values that are grayed out but simply will use the new default value set in the CWP as long as "Use System Default" is checked. A large majority of the CWP do not require a restart as they will be enabled after the cache is refreshed in about 20 seconds.
Stephen HughesBroadcom Support