(cross post) please read and vote <https://dev.luc...
# lucee
z
b
My experience with Lucee updates has been a bit mixed in terms of knowing if/when it has completed... Sometimes the spinner pops up and then quite quickly the overview page loads showing the new version information. But sometimes, like now, the page never reloads and I'm left wondering how long to let it run... This is happening (now) on both my Windoze laptop and one our Linux servers we use for QA testing. Just wondering what other people's experience is like...
z
yeah it's a bit wonky. the update process basically restarts which is a bit meh
b
My patience ran out and I clicked on the overview links... My Windoze machine was fine but I have killed the QA server... 😞
image.png
z
that's with 5.4?
b
yep...
z
which java version?
b
My Wimdoze machine is running Java 11.0.2 but I don't know about the Linux box and our SysAdmin is off until Monday.
z
can you open the admin, or dump out server.java.version ?
b
Sorry... The dump above is what I get when I try to open Lucee Admin and I don't have direct access to the server itself.
But... Assuming all our QA servers are running the same Java (the three that I could check are) the linux box is running version 1.8.0_181 (Oracle Corporation) 64bit
z
which 5.4 exactly, the rc or latest snapshot
b
5.4.0.65-RC
z
i did suggest 5.4.0.74-SNAPSHOT at the top of this thread 🙂
b
Would that have made a difference?
z
well, do you think i would have made that post if it might not have?
🤷‍♂️
b
😅 - I'd try that on another QA server but our SysAdmin would be livid if I killed another server...
on the other hand... should we be running a later version of Java on our Linux servers?
z
the latest 1.8 is 372 or so
but i'd suggest you run the same in dev as in qa and prod
otherwise, works on my machine happens
b
yeah, we get a bit of that and always have our main QA server identical to production but I tend to run Dev on the latest stable Lucee and use our less important QA servers to test migration plans before going to production.
z
yeah i do the same often, then go oh fuck
🤣 1
s
we are running this snapshot in dev, looking good, rolling out to production later today because are you even alive if you're not running snapshots in production
🤣 2
b
@zackster - our SysAdmin is back today and took a look at the QA server I that broke when trying to upgrade to Lucee 5.4... He says "5.4 tries to install something called 'the felix framework' some sort of java awt windowing system and it completely falls over at that stage"
z
can you file a ticket, noting your java version
@brettpr can you at least try with the latest java 8 and report back? 1.8.0.181 was released way back in July 17, 2018 our CI runs on Java: 1.8.0_372 https://github.com/lucee/Lucee/actions/runs/5224568758/jobs/9433817558#step:20:138
b
disclaimer - I am not a sysadmin and only know enough about java & tomcat to be dangerous... our SysAdmin says the server java version is "1.8.0_281" but Lucee :runs on the version that is shipped with Lucee" which is "1.8.0_181" but upgrading Java on a QA server at this point is unlikely as we are running on borrowed time and given the apparent overheads we are not going to upgrade Java so that we can then upgrade Lucy without some performance or security reason to do so - sorry.
z
been a while since we shipped the installer with java 8, so your tomcat is also quite old, here are all the security updates pending https://tomcat.apache.org/security-9.html
b
@zackster - we eventually backed out the QA server to v5.3.9.141 to match production. After seeing the update to LDEV-4550 I have just retested the upgrade to 5.4.0.79-SNAPSHOT and can confirm that it succeeded. I am now running our application regression test set.
z
cool bananas
👍 1
b
fyi - All tests in our regression test set passed OK
z
great! thanks for letting us know!
b
thanks for the great response and getting it sorted out! 👍
z
well done @micha
🙏 1