Virtual host in Railo 4.2.1.008-5 is not processing CFML- serving up the source code

42 views
Skip to first unread message

Ivan McAvinchey

unread,
Sep 3, 2016, 11:56:12 AM9/3/16
to Lucee
I've installed Bitnami's Railo Stack 4.2.1.008-5 which is packaged with Apache.

Railo installs OK and is serving up CFML on http://localhost:8080 or http://localhost:8888 after I changed the port. I can get into the Railo administrator and add a MySQL datasource and it verifies fine.

However the problem is when I add a virtual host- Tomcat is just serving up the source code, it's not processing the CFML.

I've gone over my server.xml with a fine toothcomb but I can't find what the issue is. I've made it match my (working) Lucee 4.5 install but no go.

This is what I have for the host:

    <Host name="www.xyz.test" appBase="webapps" unpackWARs="true" autoDeploy="true">
   <Context path="" docBase="C:\git\linode04\xyz.com\trunk\" />
   <Alias>www.xyz.test</Alias>
    </Host>

Any ideas? I'm trying to get this particular version of Railo running as it is what we are using in production and it runs the site fine while I'm having issues with ORM entity loading in Lucee 4.5 (can't use Lucee 5 due to FW/1 incompatibility).

Nando Breiter

unread,
Sep 3, 2016, 5:57:03 PM9/3/16
to lu...@googlegroups.com

(can't use Lucee 5 due to FW/1 incompatibility).

Which incompatibility?

Ivan McAvinchey

unread,
Sep 4, 2016, 7:22:20 AM9/4/16
to Lucee
I believe it's this one:


Now I'm not specifically using cfmljure but Sean still has Lucee 5 explicitly listed as "not supported" in the documentation:


I also had some other issue with Lucee 5 when I first tried it a few months back, which was solved by going back to 4.5, what specifically I can't remember.

Anyway, the point of all this is simply to try to sidestep the question of why I want to use a particular old version of Railo, why I don't just install the latest version of Lucee- I want to use it because it matches what we have in production.

I have noticed other incompatibilities, like Lucee supports direct looping over lists, which Railo doesn't (https://luceeserver.atlassian.net/browse/LDEV-47). Which is great, this is an improvement, but it does mean that when I use that code on my dev machine it works in Lucee but not in Railo when I put it up. So I want to try to have the environment as similar as possible to avoid these situations.

If you have any ideas as to what it is in Lucee (if it even is something in Lucee), or the code, or whatever else, causing the issue, I'd welcome any pointers on that as well as we do want to move to Lucee in production at some point in the future.

But for right now, I have code that works fine on Railo in production and doesn't work on Lucee on my laptop, so I want to try to get Railo working on my laptop to see if that fixes the problem.

Nando Breiter

unread,
Sep 4, 2016, 5:17:02 PM9/4/16
to lu...@googlegroups.com
You know that Railo isn't supported anymore, right? If you look for the Railo website, that's gone as well, I believe. The plug has been completely pulled. 

https://luceeserver.atlassian.net/browse/LDEV-861 won't affect you, at all, unless you want to use Clojure in your FW/1 apps. I'd check on the FW/1 Slack or google groups list what Sean means by "not supported", but I would guess that unless 861 is addressed, the FW/1 test suite is failing on Lucee 5, but I would assume that all tests not related to Clojure pass.

Comparing the Railo situation to the FW/1 on Lucee 5 situation, the latter is vastly better in terms of "supported".



Aria Media Sagl
+41 (0)76 303 4477 cell
skype: ariamedia

--
Get 10% off of the regular price for this years CFCamp in Munich, Germany (Oct. 20th & 21st) with the Lucee discount code Lucee@cfcamp. 189€ instead of 210€. Visit https://ti.to/cfcamp/cfcamp-2016/discount/Lucee@cfcamp
---
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.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/a4b8b87e-78e9-4e87-9ac1-90b46404e1af%40googlegroups.com.

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

Ivan McAvinchey

unread,
Sep 5, 2016, 5:31:33 AM9/5/16
to Lucee
@Nando- I'm aware Railo isn't supported, I'm well aware, yes, I noticed the domain was down completely when looking to download it!

The whole point though here is that I want to mirror what we are using in our production environment in my dev environment.

So if is there some bug in Railo 4.2 that causes failures, I'd actually prefer to see that immediately when writing code in my dev environment rather than it surprising me when I push the code up to production.

I included this stuff just to try to make clear why I am trying to get Railo 4.2 working, it's ultimately because that is what we are running on the production server and if there is any bug that is manifesting itself differently between the code in production and the code on my laptop, right now first thing I have to try to figure out is whether that is down to the differences between the server versions. And then I can start trying to figure out whether it is due to something else, like for example (which I've been tripped up by before) case sensitivity differences between Linux and Windows.

I'm not trying to run Railo 4.2 because I think it is better or whatever, I'm trying to run it because that is the version the code I am writing has to run on.

It doesn't make a lot of sense for me to move to Lucee 5 on my dev machine if our production server is still running Railo 4.2, it only further complicates my life.

Bilal

unread,
Sep 5, 2016, 6:41:06 AM9/5/16
to Lucee
Normally, if you see source code it would mean that the servlet mapping is not there or wrong.
Tomcat serves your cfml as static pages or is not being invoked at all.

Check out your install based on tomcat version,e.g.:

https://tomcat.apache.org/tomcat-7.0-doc/default-servlet.html

After changes to tomcat configs.
First is to try URL calls on native web port, I.e. 8888
Then the web port.

Hth,
Bilal

Reply all
Reply to author
Forward
0 new messages