Lucee 6.2.1.122 Not saving setting and red 500 on restart

dev
21

Sorry to bring back an old thread, but I want to just ask again if there was a change i the way the WAR was created for lucee 6. I ask because the version I listed above here works fine when tomcat extracts the war, but it seems like any version I tried after it, does not work correctly.

Given that it wipes out all the setting and admin password on reset, it has something to do with CFconfig?

If I start with the older version and drop in the lucee core, I do not have any issues and the upgrade works just fine. I can also copy the updated web-inf folder to the broken install and that fixes the issue (of course I have to change the password and update the dbsource).

22

just checked, there’s nothing different in the war structure aside from the lucee.jar, between 6.2.0, .6.2.1 and the latest 6.2.4 RC (published friday announcement monday)

so it must be something else in lucee itself

anyway, these kinda bug repos are difficult to follow

I’m setting up a test repo with github actions to test, if i can’t repo, can you the then fork to demo the problem?

23

I will certainly try. I saved the WEB-INF from the current release in its broken state.

24

It might help to clarify: are you still trying that on tomcat 9 (as when you started this thread) or tomcat 10 (which you later said you’d tried but had different problems with)?

25
Servlet Container Apache Tomcat/9.0.104
Java 21.0.9 (Red Hat, Inc.) 64bit
26

image
image876×581 29.8 KB

all ready for you to tweak to repo!

@carehart Tomcat 10 needs the javax jars added, Tomcat 10 is jakarta, as 6.2 is jakata compat but javax based, 7 makes the switch to being jakarta based

https://update.lucee.org/rest/update/provider/expressTemplates

these are the templates we use for express (and the installer with a few tweaks)

{

* tomcat-9: "https://cdn.lucee.org/express-templates/lucee-tomcat-9.0.111-template.zip",

* tomcat-11: "https://cdn.lucee.org/express-templates/lucee-tomcat-11.0.13-template.zip",

* tomcat-10: "https://cdn.lucee.org/express-templates/lucee-tomcat-10.1.48-template.zip"

}

just drop the lucee.jar in lib and go

27

*** I have not done RC yet but wanted to share this screen shot before I moved on ***
I downloaded all 3 wars from your links.
version 6.2.0.321 Works normally
version 6.2.1.122 went to lucee admin screen, created password.txt and put it where it needs to go, import password. Login to Lucee, click restart and get error (no need to do anything).

Here is the context directory before I press restart:

Screenshot 2025-12-06 160011
Screenshot 2025-12-06 1600111330×652 77.9 KB

Here is what it looks like after restart:

Screenshot 2025-12-06 160243
Screenshot 2025-12-06 1602431332×380 38.9 KB

I am off to see what RC does.

28

RC does the same thing, deletes a bunch of stuff on context.

29

Can you reproduce that with GitHub actions?

30

I will reset the WEB-INF and do nothing with the lucee accept import password. And I made a note on your set-password script is not setup correctly.

31

The github actions do not cause any errors. I updated set-password.cfm to work correctly as well. And I could log in with the test password.

*** Edit: And I should note this only happens after the lucee restart is clicked.

32

Try that?

33

What admin type am I to use?

34

That did it. I set adminType=1 and entered proper password. And sure enough that destroyed the context folder

35

That’s always server for restart

36

Here is the current notes on this subject:

version 6.2.0.321 Works normally
version 6.2.1.122 and 6.2.4.21-RC: went to lucee admin screen, created password.txt and put it where it needs to go, import password. Login to Lucee, click restart and get error (no need to do anything).

They both produce the same directory structure when run.

If I restart Tomcat, the web-inf folder returns back to it’s just installed state, wanting the password.txt file

If I run the 4 scripts located:
https://github.com/zspitzer/lucee-war-deploy

nothing bad happens.

If I run:
https://github.com/lucee/Lucee/blob/7.0/core/src/main/cfml/context/admin/restart.cfm

The same thing happens as if I pushed the restart link in Lucee Admin, leaving the same directory structure as shown in the above screenshots and restarting Tomcat restores missing files and puts Lucee back to password.txt.

37

Try bumping up the log level?

Are you doing applying any other config?

Did a deep review, still can’t repo, but this stands out as possibly related, if you follow that log level troubleshooting it should log that warning to the console

38

All I have done is:
take the war, drop it into webapps,
stop tomcat,
take the WEB-INF and copy it to public_html directory of webserver,
start tomcat,
put the password.txt file in context,
in the Lucee admin panel, click the restart link.

I will look into the deeper log entries.

What I do not understand is, why when it is restarted (whether it be by rebooting server, restarting tomcat, or restarting inside Lucee Admin) that is deletes the files inside the context folder. When tomcat or the server is restarted, the deleted files are restored back to defaults, where as Lucee admin just crashes out. The new files have new time stamps.

It reminds me of when one leaves the .war file in webapps and restarts tomcat, all the files are replaced with what was in the war file.

39

ahhh, eeerrghhh, why?

the WEB-INF per web-context is the old multi mode approach and Lucee did that all automatically?

the beauty of single mode is no WEB-INF under the webroot

this is a bug fixed in 6.2.1.84

https://luceeserver.atlassian.net/browse/LDEV-5420

40

The setup I used is Virualmin/Webmin. It comes with Apache and all the web services needed setup.

Then I install Tomcat (1 instance) and put the war in tomcat for extraction.

    • drop the war in webapps, it extracts itself.
    • turn off tomcat
    • copy the web-inf, meta-inf and assets to the public_html folder of the website
    • fstab bind folder from webapps to public_html
    • configure ajp for apache
    • configure server.xml hosts
    • start it all up.

This is how I have always done it. Then when I want another Lucee install, I repeat the above steps. Never had a problem until I got to a version of Lucee above 6.2.0.321.

With Lucee 7, I am now just running the installer for each installation of Lucee I want to use, and bind the lucee/tomcat/webapps/website to the public_html folder and edit the hosts.

On my next system upgrade I will be converting all my sites to individual lucee installs with their own ports. Since Tomcat will always use the same amount of resources whether it is one tomcat many lucees or many lucee/tomcats it does not matter. The only benefit is when one site crashes tomcat it won’t take them all with it.

By the same resources I mean, 1 site takes X amount of memory, 2 sites take X + X memory, so on and so forth, so just having multiple tomcats running is not going to take a whole lot me resources, just ports.

Then there is also the secret key for ajp, which does not need to be shared among all the ajp connectors when using multiple tomcats, and I am approaching the time where I will be marketing/selling my creations services, and therefore will not be the only one using lucee/tomcat.