Question to config.properties

Hi experts,

customer ask me how to reduce connection timeout time scale for SPS...?

There is a parameter called "net.connection.timeout=3" in the config.properties masterserver configuration file.

Is it possible to set this parameter to 0.1 and restart ms. Does this means, that all ssh (used for communication at customer) connections from ms to ra are timeout in 1 Min. ?

Thanks for advice

chris

[435 byte] By [ChRa] at [2007-11-26 18:09:15]
# 1

net.connection.timeout sets the amount of time the RA process will live for an SSH connection before the RA dies and waits for the next MS connection. There is an overhead involved in starting the RA, so if the connection attempts from the MS are frequent, it's more efficient to allow the RA to live for a while to try to catch the next MS request.

The unit of net.connection.timeout is 10 minutes, so the default is for the RA to live for 30 minutes after the MS last touches it.

So it seems this is the parameter you want. The bad news is that, on further investigation, this parameter is not used. There is an open bug on that problem. Sorry about that.

colinduplantisa at 2007-7-9 5:41:09 > top of Java-index,Administration Tools,N1 Service Provisioning System...
# 2

The net.connection.timeout is not used anywhere in the code.

The parameter to play with connection timeouts is net.connection.timeout.task.range

which has a default value of 10.

What this translates to is that the connection will timeout at some point between 10 and 11 minutes (or maybe 9-10 minutes, I don't remember very well) after the last communication on it.

You can reduce it to a smaller value but I wouldn't recommend to set it to a value less than 2 minutes as it may cause the agent to shutdown during a plan run which may result in interesting failures during the plan run especially if the agent shuts down between preflight and actual.

aj.a at 2007-7-9 5:41:09 > top of Java-index,Administration Tools,N1 Service Provisioning System...