Troubleshooting Caching Configuration
Updated: 01 July 2021
Product: Jamf Pro
The Jamf Pro server works with Ehcache and Memcached, but may encounter the following configuration errors during setup or after a Jamf Pro upgrade:
-
White screen during Jamf Pro startup with errors in the JAMFSoftwareServer.log
-
Cache configuration errors
-
Ehcache configuration errors
-
Memcached configuration errors
White Screen During Jamf Pro Startup with Errors in the JAMFSoftwareServer.log
When the Jamf Pro server displays a white screen during startup and a "Context initialization failed" error appears in the JAMFSoftwareServer.log.
To troubleshoot this issue, verify that the following properties files exist in the /WEB-INF/classes/dal directory:
-
cache.properties
-
ehcache.properties
-
memcached.properties
-
persistence.properties
Cache Configuration Errors
Symptom/Error | Explanation | Resolution |
---|---|---|
Cache type is out of sync. Make sure the value for cache.type in the dal /cache.properties file matches the value in the database. | This error occurs when the jss_memcached_endpoints and jss_cache_configuration tables do not exist or exist and have values that do not match those in the properties file. | Remove DBAPPLIED_ from the values in all of the properties files, then restart Tomcat. |
There was a problem updating the dal /ehcache.properties file. (Permission denied) | This error occurs when Tomcat does not have permission to update the ehcache.properties file. | Update the permissions for the ehcache.properties file, then restart Tomcat. |
There was a problem updating the dal /cache.properties file. (Permission denied) | This error occurs when Tomcat does not have permission to update the cache.properties file. | Update the permissions for the cache.properties file, then restart Tomcat. |
There was a problem updating the dal /memcached.properties file. (Permission denied)* | This error occurs when Tomcat does not have permission to update the memcached.properties file. | Update the permissions for the memcached.properties file, then restart Tomcat. |
Duplicate property keys are not allowed. Duplicate key is cache.type . | This error occurs when the cache.type value in the cache.properties file is duplicated. | Ensure there is only one value for cache.type , then restart Tomcat. |
Ehcache Configuration Errors
Symptom/Error | Explanation | Resolution |
---|---|---|
Duplicate property keys are not allowed. Duplicate key is ehcache.maxBytesLocalHeap . | This error occurs when the ehcache.maxBytesLocalHeap value in the ehcache.properties file is duplicated. | Ensure there is only one value for ehcache.maxBytesLocalHeap in the ehcache.properties file, then restart Tomcat. |
Duplicate property keys are not allowed. Duplicate key is ehcache.timeToIdleSeconds . | This error occurs when the ehcache.timeToIdleSeconds value in the ehcache.properties file is duplicated. | Ensure there is only one value for ehcache.timeToIdleSeconds , then restart Tomcat. |
Duplicate property keys are not allowed. Duplicate key is ehcache.timeToLiveSeconds . | This error occurs when the ehcache.timeToLiveSeconds value in the ehcache.properties file is duplicated. | Ensure there is only one value for ehcache.timeToLiveSeconds , then restart Tomcat. |
Cache maxBytesLocalHeap cannot be null. | This error occurs when there is a problem with the value that was entered for ehcache.maxBytesLocalHeap in the ehcache.properties file. | Ensure there is a value for ehcache.maxBytesLocalHeap in the ehcache.properties file, then restart Tomcat. |
Time to idle cannot be null. | This error occurs when there is a problem with the value for ehcache.timeToIdleSeconds in the ehcache.properties file. | Ensure there is a value for ehcache.timeToIdleSeconds in the ehcache.properties file, then restart Tomcat. |
Time to live cannot be null. | This error occurs when there is a problem with the value for ehcache.timeToLiveSeconds in the ehcache.properties file. | Ensure there is a value for ehcache.timeToLiveSeconds in the ehcache.properties file, then restart Tomcat. |
Memcached Configuration Errors
Symptom/Error | Explanation | Resolution |
---|---|---|
Timeout waiting for value. | This error occurs when a valid memcached endpoint was defined in the memcached.properties file, however, memcached may not be running on the endpoint. | Verify the memcached service is running on the endpoint, then restart Tomcat. |
No hosts in the list: '' | This error occurs when no memcached endpoint values were defined in the memcached.properties file. | Ensure there is at least one valid memcached endpoint defined in the memcached.properties file, remove DBAPPLIED_ if it exists, then restart Tomcat. |
Unable to parse memcached.timeToLiveSeconds properly. | This error occurs when there is a problem with the value for memcached.timeToLiveSeconds in the memcached.properties file. | Ensure there is a value for memcached.timeToLiveSeconds in the memcached.properties file, then restart Tomcat. |
Duplicate property keys are not allowed. Duplicate key is memcached.timeToLiveSeconds . | This error occurs when the memcached.timeToLiveSeconds value in the memcached.properties file is duplicated. | Ensure there is only one value for memcached.timeToLiveSeconds , then restart Tomcat. |
java.nio.channels.UnresolvedAddressException . | This error occurs when an endpoint in the memcached.properties file can not be resolved at the hostname entered. | Ensure the hostname can be resolved from the Jamf Pro server, then restart Tomcat. |