Upgrading Lucee 4.5 to 5 (originally Ralio 3.3.1) on Windows Problems

193 views
Skip to first unread message

Brook Davies

unread,
Jun 27, 2017, 1:04:14 AM6/27/17
to Lucee
Hello,

I've hit a brick wall here. I am trying to upgrade Lucee 4.5 to 5 and post upgrade am getting errors. 

After the last step (delete all JARA in C:\railo\lib,  keep the lucee-server dir, copy in lucee-5.2.1.9.jar), the service (which is still named "Apache Tomcat Railo") DOES starts, but web pages return 404 errors shown below (and log files attached):


Request for http://localhost:8888/lucee/admin/server.cfm > 404 - The requested resource is not available. - Apache Tomcat/7.0.73


Request for http://localhost/test.cfm > 404  (module IsapiModule > ExecuteRequestHandler)  c:\railo\connector\isapi_redirect-1.2.31.dll / from IIS



I installed Java 1.8 and removed the ancient 1.6 and updated environment paths to see if that would help. It didn't..


What I don't understand is that I see in some posts people talking about dropping the lucee.jar file into the /tomcat/lib/ext/ directory but the upgrade steps (http://docs.lucee.org/guides/lucee-5/upgrading-lucee-45.html) don't seem to mention that and I've put it in c:\railo\lib\. Is this wrong? 


Log files from C:\railo\tomcat\logs\ created when I start the service are included below. Do they help shed any light on this to anyone? I see some messages about "lucee/loader/servlet/LuceeServletContextListener : Unsupported major.minor version 51.0",. which leads me to believe Java 1.6 is still being used, however, I have un-uinstalled 1.6 and made sure the environment variables and registry entries all point to 1.8 (as mentioned in https://groups.google.com/forum/#!topic/lucee/2Vl0E1saMFI).  Could Lucee be pointing to Java 1.6 in a config file?


My environment variables look like this:




Any help at all is appreciated  - I am dead in the water on this (after many hours)...


Brook





commons-daemon.2017-06-26.log
host-manager.2017-06-26.log
railo-stderr.2017-06-26.log
catalina.2017-06-26.log

Jordan Michaels

unread,
Jun 27, 2017, 4:51:31 PM6/27/17
to lu...@googlegroups.com
Hi Brook,

Looking this over, you're probably dealing with a couple different issues here. However, before we dive into that, I wanted to ask if you had a specific dedication to your Windows 2008 server? Mainstream support for Windows Server 2008 ended on January 13th, 2015. You'll still get security patches for a couple more years, but rather then put a lot of time into upgrading this old Railo build, maybe this is a good time to start from a clean slate with a newer version of Windows? Once things are set up on a modern version of Windows, you could just migrate your app to the new server and be done with it for the foreseeable future?

Just a thought. If you want to stick with 2008 say the word I'll be happy to help you get this version working.

My initial thoughts:

1) You should probably swap out the old mod_jk connector (isapi_redirect.dll) with the BonCode Connector
2) Upgrading your JRE is a good thing. Did you configure the Tomcat service to use the updated JRE?
3) There are some minor differences between Lucee Express Edition and the Lucee Installer. I believe the difference between /tomcat/lib/ext/ and C:/lucee/lib is one of those differences.

--
Kind regards,
Jordan Michaels
Vivio Technologies

----- Original Message -----
From: "Brook Davies" <broo...@gmail.com>
To: "Lucee" <lu...@googlegroups.com>
Sent: Monday, 26 June, 2017 22:04:14
Subject: [Lucee] Upgrading Lucee 4.5 to 5 (originally Ralio 3.3.1) on Windows Problems

Hello,

I've hit a brick wall here. I am trying to upgrade Lucee 4.5 to 5 and post
upgrade am getting errors.


- Windows 2008 Web Server with IIS 7.5.
- Tomcat 7.0.73
- Java 1.6 (updated to 1.8, see below for details)
- Originally Railo 3.3.1 > upgraded to Lucee 4.5 by following
- I then tried to upgrade 4.5 to Lucee 5 by following these simple steps
(http://docs.lucee.org/guides/lucee-5/upgrading-lucee-45.html)

After the last step (delete all JARA in C:\railo\lib, keep the
lucee-server dir, copy in lucee-5.2.1.9.jar), the service (which is still
named "Apache Tomcat Railo") DOES starts, but web pages return 404 errors
shown below (and log files attached):


*Request for http://localhost:8888/lucee/admin/server.cfm > *404 - The
requested resource is not available. - Apache Tomcat/7.0.73

<https://lh3.googleusercontent.com/-mtQRzdMTeMg/WVHgKxkrV-I/AAAAAAAAA1M/G_wZYOR_Zj4pXTQuk-GKjBi93Un_87-jgCLcBGAs/s1600/tomcat.png>

*Request for http://localhost/test.cfm* > 404 (module IsapiModule >
ExecuteRequestHandler) c:\railo\connector\isapi_redirect-1.2.31.dll / from
*IIS*


<https://lh3.googleusercontent.com/-qpUD_0Nhqok/WVHgOGEG9OI/AAAAAAAAA1Q/VNFjqjr5zMo8Eu44xDcLt_vUEPAkE7IvgCLcBGAs/s1600/iis.png>


I installed Java 1.8 and removed the ancient 1.6 and updated environment
paths to see if that would help. It didn't..


What I don't understand is that I see in some posts people talking about
dropping the lucee.jar file into the /tomcat/lib/ext/ directory but the
upgrade steps
(http://docs.lucee.org/guides/lucee-5/upgrading-lucee-45.html) don't seem
to mention that and I've put it in c:\railo\lib\. *Is this wrong? *


*Log files from C:\railo\tomcat\logs\ created when I start the service are
included below*. Do they help shed any light on this to anyone? I see some
messages about "*lucee/loader/servlet/LuceeServletContextListener :
Unsupported major.minor version 51.0",. *which leads me to believe Java 1.6
is still being used, however, I have un-uinstalled 1.6 and made sure the
environment variables and registry entries all point to 1.8 (as mentioned
in https://groups.google.com/forum/#!topic/lucee/2Vl0E1saMFI). Could Lucee
be pointing to Java 1.6 in a config file?


My environment variables look like this:


<https://lh3.googleusercontent.com/-_glCqlHwHck/WVHmCyiAWXI/AAAAAAAAA10/xGmWrDUM_ngd7tPy_I-I46mWkARDVIn3ACLcBGAs/s1600/2017-06-26_21-54-50.png>



Any help at all is appreciated - I am dead in the water on this (after
many hours)...


Brook




--
###################################################################
#
# Ann: the mailing list has been migrated to the Lucee Dev forum at https://dev.lucee.org
#
###################################################################
---
You received this message because you are subscribed to the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Brook Davies

unread,
Jun 27, 2017, 6:59:11 PM6/27/17
to lu...@googlegroups.com
Hey Jordan,

Thanks for the reply! For now I have to stick with Windows 2008. Thats out of my control.  

To answer your questions:

1) You should probably swap out the old mod_jk connector (isapi_redirect.dll) with the BonCode Connector

- ok, I could try that. I assume I could just google how to do it.

2) Upgrading your JRE is a good thing. Did you configure the Tomcat service to use the updated JRE?

No, I wasn't sure where I need to make those changes, and I feel like thats part of the problem. 

3) There are some minor differences between Lucee Express Edition and the Lucee Installer. I believe the difference between /tomcat/lib/ext/ and C:/lucee/lib is one of those differences.

I don't think I am using the "Express Edition"? I never meant too. I gotta admit, its starting to look like it might be easier for me to just wipe out this install and re-install Lucee. Do you agree? Should I just uninstall everything and run the most stable build installer? 

Thanks for the help with this!

Brook





To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
###################################################################
#
#  Ann: the mailing list has been migrated to the Lucee Dev forum at https://dev.lucee.org
#
###################################################################
---
You received this message because you are subscribed to the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.

Brook Davies

unread,
Jun 28, 2017, 1:03:11 PM6/28/17
to lu...@googlegroups.com
I ended up uninstalling and re-installing. Worked great, so far so good. 

I've been looking now at securing/locking down Lucee.  Reading http://docs.lucee.org/guides/cookbooks/lockdown-guide.html it talks about locking down the admin using an Apache directive but it doesn't say where to add those entries. Where should they go? Also, do I need the WEB-INF dir? Can it be secured? 

Do you know of any other good guides on securing Lucee?

Brook Davies

unread,
Jun 28, 2017, 1:07:56 PM6/28/17
to lu...@googlegroups.com
Never mind on the Apache question, obviously thats only relevant for Apache servers and we're using IIS. I followed the request filtering lockdown instructions for the admin pages, still not sure if WEB-INF needs more security...

Jordan Michaels

unread,
Jun 28, 2017, 2:35:37 PM6/28/17
to lu...@googlegroups.com
I wrote a blog post about locking down the admins back in the railo days that is still relevant. The method can be used with Lucee in the same way it was used with Railo. Here's the post:
http://utdream.org/post.cfm/how-to-block-access-to-railo-3-4-administrators-in-iis-7-security

For the WEB-INF, it's protected by tomcat by default, so it's not a very significant security risk. If you just want to be on the safe side, you can update your Tomcat web.xml file and have all your WEB-INF directories for all your contexts created in a non-web-accessible folder on your server. Usually the folks that do that are the folks that are pulling from a common code location for many sites, but it will also simply relocate the WEB-INF if that's what you're looking to do. The parameter is documented in your web.xml file for the CFMLServlet definition.

Hope this helps!
>>> an email to lucee+un...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>> --
>>> ###################################################################
>>> #
>>> # Ann: the mailing list has been migrated to the Lucee Dev forum at
>>> https://dev.lucee.org
>>> #
>>> ###################################################################
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "Lucee" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to lucee+un...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>

--
###################################################################
#
# Ann: the mailing list has been migrated to the Lucee Dev forum at https://dev.lucee.org
#
###################################################################
---
You received this message because you are subscribed to the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages