![]() ![]() Internal testing suggests that this one-time change may take roughly 20 extra minutes per 15 million rows in these two tables combined, depending on the hardware used in your environment. The session-timeout value is now configurable in the session.properties configuration file as a "number of seconds value", for example session.maxInactiveIntervalInSeconds=1800Ī database schema change will be made to add a new id column to the extension_attribute_values and mobile_device_extension_attribute_values tables when upgrading to Jamf Pro 10.19.0 or later. As a result, Jamf Pro sessions no longer respect the session-timeout value in web.xml and, by default, will timeout after 1800 seconds (30 minutes). ![]() User session management was updated to support clustered sessions. If you have questions or experience any issues during this process, contact Jamf Support. To prevent database issues that could require restoring from a backup, it is important that you do not stop Tomcat or downgrade. This one-time change could cause an increase in startup time, depending on the amount of smart and static groups and the hardware used in your environment. ![]() Ubuntu Server 18.04 LTS was moved to the Minimum Supported compatibility level.Ī database schema change will be made to update which tables groups are stored in. Ubuntu Server 20.04 LTS was added to the Recommended compatibility level. Added support for Ubuntu Server 20.04 LTS ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |