OS: Windows 11 Pro
Java Version: 21.0.6 (Eclipse Adoptium) 64bit
Tomcat Version: Apache Tomcat/10.1.36
Lucee Version: 6.2.0.321
Web Server: IIS
Last year, I posted about an issue I was having with Multi Mode when upgrading from 5.4 to 6 ( Attempting to Update Lucee from 5.4.3.2 or 5.4.5.23 to 6.0.1.83 results in error - support - Lucee Dev ). With the impending end to LTS for 5.4 at the end of the year, I had to tackle this again, and, again, I am facing the same problem I was at the end of that post: context settings not getting saved. In order to troubleshoot this, I did a fresh install of Windows 11 and a fresh install of IIS & Lucee 6 (no 5.4 involved). The problem remains. Here are the steps I took:
- Installed Windows
- Installed IIS
- Installed Lucee 6.2.0.321
- Visited http://127.0.0.1:8888/index.cfm (welcome page worked fine)
- Visited IIS default local site (The Lucee welcome page initially errored out, but replacing it with basic cfoutput of Now() proved Lucee was connected.)
- Opened Lucee admin
- Switched to Multi Mode
- Added “C:\inetpub\wwwroot” individual context for IIS default local site
- Made changes
- Saved changes
- Reopened individual context settings: No changes saved
- Restarted Lucee
- Visited IIS default local site to trigger Lucee admin to recognize the context
Result: Configured context no longer listed under “specific web contexts”, but had returned to “create new web context” drop down.
It appears as though, even on a fresh install, Lucee isn’t saving individual context settings. Other oddities I’ve noted:
All changes are saved to “C:\lucee\tomcat\lucee-server\context.CFConfig.json”, but the admin doesn’t display or enforce them.
The default Lucee welcome page did eventually load via IIS, but gave this message: “Warning, if you can see this message, your webserver webroot is not mapped to [C:\inetpub\wwwroot]. This means Lucee is only configured to handle .cfm and .cfc and other files like css, js and images won’t load properly.” This happened regardless of whether or not I had defined that context, but I think that’s more about assets not being copied alongside the index.cfm than a context configuration issue.
If I change the General context settings, those settings will be applied to any new specific context that I create. Security settings made this way will be enforced in the specific context, even if the General context setting is changed, but they cannot be modified. Restarting Lucee resets enforcement to whatever the General context is set to. So, it appears to acknowledge the context, without allowing further modifications, but only until a service restart.
If I switch the General context to “Local” and add an external folder, it will also automatically add C:\Lucee\tomcat\Lucee-server\context\temp.
Is no one else running into this?