[
https://issues.apache.org/jira/browse/CLOUDSTACK-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056437#comment-14056437
]
ASF subversion and git services commented on CLOUDSTACK-6261:
-------------------------------------------------------------
Commit e07d0ddabfedad137856c3c9ae7de3a96fe25feb in cloudstack's branch
refs/heads/master from Sujaya Maiyya
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e07d0dd ]
fixed CLOUDSTACK-6261: remove the forceful timeout setting when login to
NetScaler.
> remove the forceful timeout setting when login to NetScaler
> -----------------------------------------------------------
>
> Key: CLOUDSTACK-6261
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6261
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Devices
> Affects Versions: 4.4.0
> Environment: NetScaler VPX/MPX 10.5+ (code does not force timeout
> when login to SDX)
> Reporter: Vijay Venkatachalam
> Assignee: Rajesh Battala
> Priority: Minor
> Labels: patch
> Fix For: 4.4.0
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Today, the NetScaler Resource forces a idle timeout of 100,000 seconds (~1
> day and 4 hours) during login. The request is to remove forcing the timeout
> to a specific value.
> Also, future versions of NetScaler is planning to have a cap of 1 day for
> this setting.
> It is best to leave it to the system default which is 30 mins. This should be
> enough, anyway there are threads for monitoring of member status, and
> statistics collections that keeps the session alive and it is unlikely to
> gather idle time.
> The NetScaler resource already handles timeout expiry using retries so there
> should not be any see side effects by leaving the idle time out to be the
> default value 30 mins..
--
This message was sent by Atlassian JIRA
(v6.2#6252)
