I built a version from source to do a clean war deployment on Tomcat. I’ll blog about it tomorrow if I can, here are some suggestions for places to check your config. You should be able to do the same thing with the war download from the Lucee site.
tomcat/conf/web.xml: make sure you have your config updated. In this case I took the Railo definitions and did search/replace Railo->Lucee and railo->lucee.
LuceeCFMLServlet
CFML runtime Engine
lucee.loader.servlet.CFMLServlet
configuration
/WEB-INF/lucee
Configuration directory
1
LuceeAMFServlet
AMF Servlet for flash remoting
lucee.loader.servlet.AMFServlet
1
LuceeFileServlet
File Servlet for simple files
lucee.loader.servlet.FileServlet
2
tomcat/conf/catalina.properties:
#common.loader=${catalina.home}/lib,${catalina.home}/lib/.jar,${catalina.home}/railo,${catalina.home}/railo/.jar
common.loader=${catalina.home}/lib,${catalina.home}/lib/.jar,${catalina.home}/lucee,${catalina.home}/lucee/.jar
I created ${catalina.home}/lucee by extracting the war and copying the contents of WEB-INF/lib into the tomcat/lucee folder.
tomcat/conf/setenv.sh
JAVA_OPTS="-Xms256m -Xmx1024m -XX:MaxPermSize=128m -javaagent:${CATALINA_HOME}/lucee/lucee-inst.jar”;
Go into tomcat/webapps. Remove ./ROOT, rename the lucee war file ROOT.war, copy it into ./webapps. Start Tomcat. Goto http://servername:8080//lucee/admin/server.cfm. (Unless you are running Tomcat on another port, e.g. 8888, or proxying through Apache/Nginx, etc.).
Remove the old WEB-INF folder from any other web doc roots.
This is very preliminary and may contain mistakes, when I can I will do a blog and video post with more complete instructions.On Feb 20, 2015, at 8:16 PM, Jason Tully <@Jason_Tully> wrote:
I have this same issue, and can’t update our production servers until its fixed. Sadly, the solution you suggested did not work for me.
On Tuesday, February 10, 2015 at 3:19:27 PM UTC-5, Jake Hand wrote:
Just wanted to post a quick solution for an issue I encountered during a Lucee conversion, in case anyone else runs into it.
Essentially what had happened was we followed the conversion guide to convert a Railo 4 on Tomcat installation to Lucee, but none of the sites on the server had their datasources after the conversion. When we checked each site’s WEB-INF folder, it still had a railo subfolder instead of one named lucee. Within the WEB-INF/railo folder for each site there was a file named lucee-web.xml.cfm but it didn’t have any of the settings from the corresponding railo-web.xml.cfm file.
It turns out the problem was this init-param setting for the GlobalCFMLServlet within Tomcat’s web.xml:
<init-param>
<param-name>railo-web-directory</param-name>
<param-value>{web-root-directory}/WEB-INF/railo/</param-value>
<description>Railo Web Directory directory</description>
</init-param>
When we commented that out and restarted Tomcat Lucee handled the conversion for each site (context) as expected. Each site ended up with a WEB-INF/lucee folder, and the lucee-web.xml.cfm file had all the datasources and other settings in-tact. This might elicit a “Well, duh.” response from some of the more experienced users out there, but I wanted to share in case anyone else encounters a similar issue.
Best,
Jake
–
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 lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/0b0d46d0-684d-43c4-b3ef-96e78eada424%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.