Our Bladelogic Environment, recently migrated to 8.9.01, keeps kicking the users out, and forcong them to enter the password again.
It also happened on previous versions.
On our first bmccase, they suggested to change some blasadmin parameters and restart. We realized here, that after restarting, it took a while untill the environment started behaving the same.
So those parameters seemed not to be the ones, but we saw that restart the platform somehow, stops that behavior for a while.
Now, we have opened a second case, and they have told us to change these parameters:
Anybody knows which are the parameters that really affects to the BSA Console desconnection when using the environment?
Or if it is something else that may affect?
To adjust the performance of proxy threads processing Network Shell
connections, specify a maximum idle time for thread processing. To
this, enter the following:
set appserver NshProxyMaxThreadIdleTime #
where # can be any of the following:
0 – Provides the best thread switching
performance. A thread is always available to
serve another connection after traffic ends on the current connection.
-1 – Provides the fastest performance for a
particular connection. Each thread is
dedicated to a single connection so the thread never switches
>0 – Provides a compromise between the two
settings described above. A value
greater than zero specifies a period, in milliseconds, that a thread should remain
- idle. While the thread is idle it continues to serve the current
connection. When the
specified period expires, the thread can switch to another connection.
you instruct a thread to be idle, the harder it is for that thread to
process more than
By default NshProxyMaxThreadIdleTime is
set to 500 ms.
specify the duration of session credentials that the Authentication Service
enter the following:
AuthServer SessionCredentialLifetime #
# is the lifetime, in minutes, of issued session credentials. By
session credential lifetime is 600 minutes (10 hours).