All work

 
7 of 7

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

Fixed

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

Details

Assignee

Reporter

Priority

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Affects versions

Created 1 November 2019 at 20:45
Updated 14 April 2023 at 11:48
Resolved 28 August 2020 at 10:20

Activity

Michael Offner28 August 2020 at 10:20

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

Michael Offner28 August 2020 at 10:18

Brad Wood1 November 2019 at 21:50

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

Brad Wood1 November 2019 at 20:53

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.

John Wilson1 November 2019 at 20:47

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