OK, here's the example. You could overwrite the default on a specic application by configuring the inactivty time on that application.
I configured this apply group (setting timeout to 15 minutes):
app-timeout {
applications {
application <*> inactivity-timeout 15;
}
}
To configure this: set groups app-timeout applications application <*> inactivity-timeout 15
My applications look like this
apply-groups app-timeout;
application app1 {
protocol tcp;
destination-port 234;
}
application app2 {
protocol tcp;
destination-port 345;
}
( set applications apply-group app-timeout to apply the group on youe definition)
To show the result:
root@vr-device# show applications | display inheritance
application app1 {
protocol tcp;
destination-port 234;
##
## '15' was inherited from group 'app-timeout'
##
inactivity-timeout 15;
}
application app2 {
protocol tcp;
destination-port 345;
##
## '15' was inherited from group 'app-timeout'
##
inactivity-timeout 15;
}
Be aware that some applications don't handle broken connections very well. so putting all your application on a tight time-out might result in errors at some applications.