upgrading to 5

[Franc Amour]

I have lucee running on mac OS X (El Cap), and would like to upgrade to version 5.

I saw this document:

http://docs.lucee.org/guides/lucee-5/upgrading-lucee-45.html

But I am not sure of exactly which directory I should be working in.  I already have the JAR file, but since this also involves *deleting* jar files, i need to make sure i'm in the right place.

Can anyone else on mac verify where (from the top level "tomcat" directory) where I need to be?

[Jordan Michaels]

For better or worse there are lots of ways to go about installing Lucee. In order for us to help you with this question we would need to know more about your current setup. How did you install Lucee on your Mac? Did you follow a specific set of instructions?

We're happy to help but without knowing the basics of your setup there's not much we can do.

--
Kind regards,
Jordan Michaels
Vivio Technologies

--
Win a ticket to dev.objective from Lucee via Twitter, see http://bit.ly/1UbTMWj for details, good luck and see you there...
---
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.
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/f37e1fe4-d498-40d4-b36d-1cbd0e6d94df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Franc Amour]

It was just long enough ago that I don't remember exactly what I did, and while I know I documented the process, I can't seem to find the document.  So if it helps... I believe the entire installation is self-contained in the tomcat directory, directly under my user directory.  That tomcat directory contains a lucee directory with a metric ton of .jar files and a lucee-server directory.

[Andrew Penhorwood]

Stop Tomcat / Lucee

Is the lucee folder the one with a Lucee.jar file?  If so then that is the right place.  Remove all of the jar files in that folder.  Leave the lucee-server folder as that contains your configuration files.  Place the Lucee 5.x jar file (there is only one of these) in the same place where you deleted the other files.

Start Tomcat / Lucee

The Lucee 5.x stuff will expand and write its various stuff.  This process can take a minutes or two.  Once that is complete your Lucee server should be up and running on version 5.x.

Andrew Penhorwood 

[Franc Amour]

It looks like i have two directories that contain a lucee.jar file:


/Users/[ME]/tomcat/lucee

AND

/Users/[ME]/tomcat/webapps/ROOT/WEB-INF/lib

I tried the first, then the second and in each case the lucee 5 jar file i downloaded did not expand when i start tomcat back up, and all sites go 503.  I put my copies of those directories back, and restarted tomcat, and it looks like i've hosed myself - apache just throws an error now when i load a site that was working:

HTTP Status 500 - Servlet.init() for servlet CFMLServlet threw exception

---

type Exception report

message Servlet.init() for servlet CFMLServlet threw exception

description The server encountered an internal error that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: Servlet.init() for servlet CFMLServlet threw exception
	org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
	org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
	org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:436)
	org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:190)
	org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
	org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
	java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.lang.Thread.run(Thread.java:745)

root cause

java.lang.NoClassDefFoundError: org/osgi/framework/Bundle
	java.lang.Class.getDeclaredMethods0(Native Method)
	java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
	java.lang.Class.privateGetMethodRecursive(Class.java:3048)
	java.lang.Class.getMethod0(Class.java:3018)
	java.lang.Class.getMethod(Class.java:1784)
	lucee.loader.engine.CFMLEngineFactory.getEngine(CFMLEngineFactory.java:749)
	lucee.loader.engine.CFMLEngineFactory.initEngine(CFMLEngineFactory.java:288)
	lucee.loader.engine.CFMLEngineFactory.getEngine(CFMLEngineFactory.java:228)
	lucee.loader.engine.CFMLEngineFactory.getInstance(CFMLEngineFactory.java:102)
	lucee.loader.engine.CFMLEngineFactory.getInstance(CFMLEngineFactory.java:155)
	lucee.loader.servlet.CFMLServlet.init(CFMLServlet.java:41)
	org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
	org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
	org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:436)
	org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:190)
	org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
	org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
	java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.lang.Thread.run(Thread.java:745)

root cause

java.lang.ClassNotFoundException: org.osgi.framework.Bundle
	java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	lucee.loader.classloader.LuceeClassLoader.loadClass(LuceeClassLoader.java:173)
	lucee.loader.classloader.LuceeClassLoader.loadClass(LuceeClassLoader.java:138)
	java.lang.Class.getDeclaredMethods0(Native Method)
	java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
	java.lang.Class.privateGetMethodRecursive(Class.java:3048)
	java.lang.Class.getMethod0(Class.java:3018)
	java.lang.Class.getMethod(Class.java:1784)
	lucee.loader.engine.CFMLEngineFactory.getEngine(CFMLEngineFactory.java:749)
	lucee.loader.engine.CFMLEngineFactory.initEngine(CFMLEngineFactory.java:288)
	lucee.loader.engine.CFMLEngineFactory.getEngine(CFMLEngineFactory.java:228)
	lucee.loader.engine.CFMLEngineFactory.getInstance(CFMLEngineFactory.java:102)
	lucee.loader.engine.CFMLEngineFactory.getInstance(CFMLEngineFactory.java:155)
	lucee.loader.servlet.CFMLServlet.init(CFMLServlet.java:41)
	org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:505)
	org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
	org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:436)
	org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:190)
	org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)
	org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
	java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.lang.Thread.run(Thread.java:745)

Looks like i've really done it this time! =D

[Andrew Penhorwood]

This is the folder you need.  Put the jar file there.  The other one is the per site location stuff.  

/Users/[ME]/tomcat/lucee

http://cdn.lucee.org/rest/update/provider/loader/5.0.0.252  - This is the jar file I am talking about.

The other files should reset themselves I believe.  At the most you might have lost your settings.

Andrew Penhorwood

[Franc Amour]

Removed all jars from /Users/[ME]/tomcat/lucee, left the lucee-server folder.

Ran startup.sh and this was the output:

~/tomcat/bin $ ./startup.sh
Using CATALINA_BASE:   /Users/me/tomcat
Using CATALINA_HOME:   /Users/me/tomcat
Using CATALINA_TMPDIR: /Users/me/tomcat/temp
Using JRE_HOME:        /Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home
Using CLASSPATH:       /Users/me/tomcat/bin/bootstrap.jar:/Users/me/tomcat/bin/tomcat-juli.jar
Tomcat started.

jar file was not expanded - only the lucee-5.0.0.252.jar file and the lucee-server directory remain in the directory.  All local sites still result in 503 Service Unavailable.

Then ran shutdown.sh and this was the output:

/tomcat/bin $ ./shutdown.sh
Using CATALINA_BASE:   /Users/me/tomcat
Using CATALINA_HOME:   /Users/me/tomcat
Using CATALINA_TMPDIR: /Users/me/tomcat/temp
Using JRE_HOME:        /Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home
Using CLASSPATH:       /Users/me/tomcat/bin/bootstrap.jar:/Users/me/tomcat/bin/tomcat-juli.jar
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
objc[23305]: Class JavaLaunchHelper is implemented in both /Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home/bin/java and /Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home/jre/lib/libinstrument.dylib. One of the two will be used. Which one is undefined.
Error opening zip file or JAR manifest missing : /Users/me/tomcat/lucee/lucee-inst.jar
Error occurred during initialization of VM
agent library failed to init: instrument

Would like to get rid of the 64-Bit Server VM warning, but more concerning is the referecne to the missing lucee-inst.jar file of course.

[Andrew Penhorwood]

Is this folder /Users/me/tomcat/lucee/ the server folder or one of the context (web) folder?

[Franc Amour]

how would i be able to tell?  server as in tomcat, or server as in lucee?  It's still pretty confusing, coming from an ACF background where installers were the norm.

Since Apache is working fine, i wonder if I should just wipe out tomcat/lucee config somehow and start over... this shouldn't be as hard as it has become.  is there really that few people needing to set this up on mac?

[Nando Breiter]

Franc,

I installed Lucee 5 on my Mac using the express version, very simple to install, but I don't bother with a web server on my dev environment. ACF 10 is on 8500, ACF 11 is on 8501, Lucee 5 is on port 8888, and Lucee 4.5 is on port 80, all via Tomcat. 

Aria Media Sagl

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

On Fri, Jul 8, 2016 at 9:47 PM, Franc Amour <advan...@gmail.com> wrote:

how would i be able to tell?  server as in tomcat, or server as in lucee?  It's still pretty confusing, coming from an ACF background where installers were the norm.

Since Apache is working fine, i wonder if I should just wipe out tomcat/lucee config somehow and start over... this shouldn't be as hard as it has become.  is there really that few people needing to set this up on mac?

--

Win a ticket to dev.objective from Lucee via Twitter, see http://bit.ly/1UbTMWj for details, good luck and see you there...
---
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.
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/97da7a85-5c57-4eb0-aeb2-ebfb14a79ebe%40googlegroups.com.

[Franc Amour]

Okay, I gave up on having a local environment close to my production environment, and have downloaded and run Lucee 5 Express.  Works fine.

Now, how do i set up Tomcat/Lucee to serve up my sites that I already have in my /Volumes/Sites directory?  Is it a matter of editing the tomcat web.xml and server.xml files?  And how do i access the Tomcat Administrator?

[Nando Breiter]

Now, how do i set up Tomcat/Lucee to serve up my sites that I already have in my /Volumes/Sites directory?  Is it a matter of editing the tomcat web.xml and server.xml files? 

What I've done is edit server.xml, toward the bottom you'll find a Host declaration for localhost. Set the docBase attribute of the Context tag to /Volumes/Sites, as below. Restart Lucee to pick up the change.

     <Host name="localhost"  appBase="webapps"

            unpackWARs="true" autoDeploy="true">

        <!-- SingleSignOn valve, share authentication between web applications

             Documentation at: /docs/config/valve.html -->

        <!--

        <Valve className="org.apache.catalina.authenticator.SingleSignOn" />

        -->

        <!-- Access log processes all example.

             Documentation at: /docs/config/valve.html

             Note: The pattern used is equivalent to using pattern="common" -->

        <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"

               prefix="localhost_access_log" suffix=".txt"

               pattern="%h %l %u %t &quot;%r&quot; %s %b" />

          <Context path="" docBase="/Volumes/Sites" />

      </Host>

I'd then navigate to localhost:8888/site1/ for instance to work on "site1" on my dev machine.

 

And how do i access the Tomcat Administrator?

Do you mean the Lucee administrator? If so, you'll find it at http://localhost:8888/lucee/admin/server.cfm for the server context and http://localhost:8888/lucee/admin/web.cfm for the web context. For local development, I use only the server context and a single web context (the one defined above at localhost). Note that scheduled tasks are located in the web context only. All other settings you'll find in the server context, such as datasources for instance.

Separate web contexts potentially provide added security in production. You could give the password to a separate web context to another developer, for instance, without giving him or her access to any other web context or the server context. So far, I've deployed all domains to a single web context to keep things simple for me.

In production, I also would simply install Lucee using the express installer, and configure host declarations for each domain, similar to the following:

<Host name="domain.com" appBase="webapps">
    <Context path="" docBase="/var/sites/domain.com" />
    <Alias>www.domain.com</Alias>
</Host>

I know many folks prefer to use mod_cfml. I somehow find it more simple to configure sites directly. In the same vein, I use Nginx rather than Apache, because I find the configuration syntax to be more simple and direct in Nginx.

--
Win a ticket to dev.objective from Lucee via Twitter, see http://bit.ly/1UbTMWj for details, good luck and see you there...
---
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.
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/78687526-97b3-4cb4-beb9-c6314a6917a9%40googlegroups.com.

[Franc Amour]

Thanks, you confirmed quite a few things for me.  In my case, i do have a separate context (WEB-INF) for each site. 

I found for some reason that when adding the hosts to server.xml, tomcat wouldn't load - found that it seems like an old bug or something, as this URL fixed my problem:

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

which means each of my host entries now look like this:

<Host name="www-example-com" appBase="webapps" unpackWARs="true" autoDeploy="true">
  <Context path="" docBase="/Volumes/Storage/company/sites/example-com/www">               
  <JarScanner scanClassPath="false"/>
  </Context>
</Host>   

And because i hate urls that don't match production and sites having to run under subdirectories, I installed and configured haProxy via homebrew, and set it up to forward all port 80 requests to tomcat on 8888.

Combined with my hosts file entries (e.g., "127.0.0.1 www-myapp-com"), I have what looks awful lot like a production environment with each site remaining isolated and the urls looking the same.  So far so good, but it's only been about 15 minutes or so, lol. 

Now i can access dev sites using simply

http://www-example-com

and the lucee admin for that site is under

http://www-example.com/lucee/admin/web.cfm.

Still not sure how future upgrades of Lucee will work under this configuration, but as long as i back it up, it's easy enough now to start from scratch with a fresh express download and just copy over the server.xml file.

Tomcat also has (or had, anyway) it's own admin/manager area, but i don't recall using it for anything anyway.  Used to be something like:

http://localhost:8080/manager/html

Thanks for your help, all.  Now I just need to figure out how to get HaProxy, tomcat, and mysql to all launch upon bootup and I'll be good to go.

[Nando Breiter]

Franc,

Updating Lucee should work without issue. Go to the server.cfm admin panel and run the update from there. Stick to stable releases if you want to be sure nothing will break. The upgrade from 4 to 5 tripped you up, but the normal updates are a different story.

Have you worked out a way to run different engines in parallel? ACF 11 and Lucee 5 for instance? 

Aria Media Sagl

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

--
Win a ticket to dev.objective from Lucee via Twitter, see http://bit.ly/1UbTMWj for details, good luck and see you there...
---
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.
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/aaf42e7e-e564-4197-855e-320a43d3f62a%40googlegroups.com.

[Franc Amour]

Yes, I assume the patches would come down via the admin update function without issue.. but major releases, hopefully, will also get easier to upgrade to.

I haven't really needed to run any in parallel - all my sites are going to Lucee at this point.

A new issue has cropped up - it appears (for example, when loading images) that there's some case-sensitivity going on here - in the code there's a few image references where the path is correct but the folder name is capitalized, which is causing tomcat to not find the image.  Any way to turn off this case-sensitivity? I'm sure there's a lot of code right now that has such things going on and I am not going to be able to go through all these sites and fix them for something like that...

[Nando Breiter]

 Any way to turn off this case-sensitivity? 

No idea on my end. I deploy to Linux and so am always mindful of case sensitivity. I'd use a global search and replace to correct the code to match the file system.

[Franc Amour]

just not an option - though my OCD would love to ;)

Is there a way to get Lucee Express to use Apache?

[Nando Breiter]

Haven't done that, but you can start here: http://www.modcfml.org/

and here: https://tomcat.apache.org/connectors-doc/common_howto/proxy.html

The 2 ways I've heard of are mod cfml and a reverse proxy setup. The second link is a hit from searching for "reverse proxy apache tomcat".

I think I said I use Nginx in a reverse proxy configuration, so that's what I'm most familar with. 

Aria Media Sagl

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

--

Win a ticket to dev.objective from Lucee via Twitter, see http://bit.ly/1UbTMWj for details, good luck and see you there...
---
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.
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/6ce1a88d-8e8a-4d27-abb4-977b0870b843%40googlegroups.com.