Skip to main content
Support

KB Article #176100

Connection filter - cannot change connection establishment timeout from default 3000ms

Problem

The connection filter cannot establish the connection to the backend because the default timeout is 3000ms which is too short and cannot be changed.


Example of error found in trace :-


DEBUG 01/01/2014 12:00:00.257 run filter [Connection to backend] {
DEBUG 01/10/2014 12:00:00.258 get connection to host 10.0.0.9 port 1000 scheme http
DEBUG 01/01/2014 12:00:00.258 new endpoint: 10.0.0.9:1000
DEBUG 01/01/2014 12:00:00.258 Resolved 10.0.0.9:1000 to:
DEBUG 01/01/2014 12:00:00.258 10.0.0.9:1000
DEBUG 01/01/2014 12:00:00.258 poll() with max timeout 3000
ERROR 01/01/2014 12:00:00.261 connection timed out after 3000ms
ERROR 01/01/2014 12:00:00.261 cannot connect to 10.0.0.23 10.0.0.9:1000: Operation now in progress
ERROR 01/01/2014 12:00:00.262 transient failure connecting to remote: : 10.0.0.23 10.0.0.9:1000: connection failed.
DEBUG 01/01/2014 12:00:00.262 Adding MessageListener: com.vordel.circuit.net.ConnectionProcessor$1@01234567
DEBUG 01/01/2014 12:00:00.262 connection processor made 1 attempts to transact
DEBUG 01/01/2014 12:00:00.262 } = 0, filter [Connect to backend]



Resolution

For 7.3 and later configure a remote host which has a field for the connection timeout.



image41751bf98da80bf6876718fc3ce31491_000.png