Application action="update" reverts sessioncluster and clientcluster to false.

Description

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.

Application.cfc

index.cfm

Compare sessioncluster, clientcluster and cgireadonly before and after the application update.

Environment

Docker, commandbox debian/ubuntu and windows

Activity

Show:
John Wilson
November 2, 2019, 7:47 AM

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


Brad Wood
November 2, 2019, 7:53 AM

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.

Brad Wood
November 2, 2019, 8:50 AM

I asked John to put in this ticket because I couldn't find the original ticket even though I remembered it existing. I finally found it here: https://luceeserver.atlassian.net/browse/LDEV-855

Michael Offner
August 28, 2020, 8:18 PM

Michael Offner
August 28, 2020, 8:20 PM

I also solved the same issue for “clientstorage” and “cgiReadOnly“

Fixed

Assignee

Michael Offner

Reporter

John Wilson

Priority

Blocker

Labels

None

Fix versions

Sprint

5.3.8 Sprint 3

Affects versions