Given the application.cfc file below, application action="update" resets sessioncluster, clientcluster and cgireadonly to their lucee defaults - not to my application settings. Adding a cf mapping kills clustering. A test index.cfm file is given below.
Compare sessioncluster, clientcluster and cgireadonly before and after the application update.
Docker, commandbox debian/ubuntu and windows
suggested that the problem likely lies here:
Here's the code. I'm just comparing settings whose default value here
is different from what gets checked here
Yes, the Java code doesn't have any checks to see if the application already had a non-default value set and simply blows away the existing settings with defaults. This basically makes session clustering useless in a ColdBox app which uses application updates heavily.
I also solved the same issue for “clientstorage” and “cgiReadOnly“