Express version doesn't "just run" here

[Dave Merrill]

Please excuse my unfamiliarity with the underpinnings of the express version, but for me, it doesn't "just run" (Win7 Pro). The included docs seem to be for some of the components used, not this package as a whole, and don't appear to address potentially necessary configuration issues. Is this supposed to work now?

I know it's early, not everything is soup yet, no criticism is intended, just want to get it running, and maybe help others who want the same. Maybe more familiarity with this infrastructure is assumed, but ideally, anyone could download the express package and be up and running with nothing but the instructions provided. At minimum, if configuration or environment setup is required, a Lucee-specific start-from-zero guide should be provided. Better error messaging would be great too.

Here's what happens here: When I just double click startup.bat, it just exits, probably expected, but if so, should be documented somewhere. If I run it from the cmd line, it reads out some environment vars, then returns to the cmd prompt, without actually starting the Lucee engine, or complaining about why it couldn't, as far as I can tell. Ran the cmd prompt as admin, no difference. The logs directory is empty.

Nothing in startup.bat appears to be machine or environment-specific, and nothing in web.xml, context.xml, or server.xml jumped out at me as needing to be edited.

Thanks for any thoughts, and again, my apologies for not knowing whatever is it that probably should be obvious to folks with more Java background. I've been working in CFML for many years, but clearly I'm missing some required info, and I'm quite likely not alone in that.

Dave

[Andrew Penhorwood]

Sorry to state what might sound obvious but is there anything running on that port?  Not sure what port the express version is running on but from your post that sounds like the issue.

Andrew Penhorwood

[Adam De Lay]

Dave,

I had the same problem you did initially.  I'm running on Win 8.1 and when I tried to run startup.bat, it opened and closed.  What I found out was that I needed to have installed (I believe) JRE 1.8 and set the JAVA_HOME env var.  Once I had that installed, then I retried running the startup.bat and it ran and opened a new command window (Tomcat) but when I looked at the log file, there was still some problem (I believe it was a binding issue because of how many times I had tried running the startup.bat).  I rebooted and then everything came up as it should when I ran the batch file.

Hopefully that helps.

Adam De Lay

On Tuesday, February 3, 2015 at 8:16:12 AM UTC-5, Dave Merrill wrote:

[Adam Cameron]

I blogged my experiences getting it working: http://blog.adamcameron.me/2015/02/lucee-hiccups-when-getting-new-express.html (I did not have the same issue as mentioned here, that said).

It'd be really good if other ppl could also blog their mission so there's more links back to Lucee, plus more material for people in future to find if/when they run into problems.

-- 

Adam

--
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/fceb57bc-d224-45fd-9eff-7cf04d89aff5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael Offner]

We did the Express Version completely new with Tomcat and we no longer provide the JRE version, so a JRE version need to be installed and JAVA_HOME need to be set.

We will shortly add more details to the wiki about all bundles we provide, we will also look into it, to provide a better experience in case it does not work.

Micha

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAFwR%2BKc1ZnsPBrRL5w0ZTYbGwwHz_fUO0Ri58kDHK1FKSweYXQ%40mail.gmail.com.

[Dave Merrill]

I have Java 1.7 installed, and the system environment var JAVA_HOME points to it.

- Does Lucee actually require 1.8? Where are the system requirements documented?

- Do I need to set JAVA_HOME somewhere in the Lucee startup script or configs, or is the system var sufficient?

Dave

[Mark Drew]

Hi Dave

In the command line do the following

> cd lucee

> cd bin

> catalina.bat run 

That should give you all the output 

otherwise just open up lucee/logs/catalina.out and that will tell you what is happening at startup

Regards

Mark Drew

-- 
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/b1da3fb3-65f0-47ba-b76c-c9ec783c370c%40googlegroups.com.

[Dave Merrill]

Thanks for the info. I do have various Railo and ACF versions and configurations installed, but CATALINA_HOME isn't set as a system environment var.

That's the only thing I saw in your post that you HAD to change to get it running, everything else was for your preferred setup, not required. Or did I miss something.

Dave

[Dave Merrill]

Thanks Mark, that was at least partially helpful. I did see an error running it that way, which I'll try to retype here; tried to pipe the result to a file, but it just echoed the environment vars, not the error.

Exception in thread "main" java.lang.UnsupportedClassVersionErrror: org/apache/catalina/startup/Bootstrap : Unsupported major.minor version 51.0
Could not find the main class org.apache.catalina.startup.Bootstrap. Program will exit.

Is this about supported Java versions? If so, and I need to install Java 1.8, but don't want to change the system environment var, where should I set JAVA_HOME so Luceee sees it? Directly in startup.bat? Some config?

Thanks again,
Dave

[Dave Merrill]

Thanks for jumping in Micah.

It just penetrated that you said there needs to be a JRE installed, which there is, but the system var JAVA_HOME points to a 1.7 JDK.
- Will a JDK work?
- Will 1.7 work?
- If I need to point to a JRE, or install a different Java version and point to it, where should I set JAVA_HOME so Lucee will see it, without changing the system var other things are looking at?

Thanks, and apologies for this low-level trivia.

Dave

[denstar]

On 02/03/2015 07:30 AM, Michael Offner wrote:
> We did the Express Version completely new with Tomcat and we no longer
> provide the JRE version, so a JRE version need to be installed and
> JAVA_HOME need to be set.
> We will shortly add more details to the wiki about all bundles we provide,
> we will also look into it, to provide a better experience in case it does
> not work.

I've added the (optional) bundles with JREs to the build, as I really
like the idea of "click- bang!" vs. the potential problems with using
system Java installs.

We're going to need to address the downloads page though, as there are
going to be options-- that's one of the reasons I want to push
"standard" as a type (or just having "Lucee" == standard), so it's clear
what is considered the standard install.

I like the idea of presenting just the "standard" downloads at first
page load (w/some JS to guess the OS-- offering without/with JRE as the
main options), with a link to the others.

:Den

[Chester Austin]

I've been following this thread since I had the same issue Dave originally had.  I happend to have JRE 1.8 installed, so the next logical question would be "What do I do this with this information?"  The answer would be to create a system variable that points to the JRE path.

Using this as a guide, https://confluence.atlassian.com/display/DOC/Setting+the+JAVA_HOME+Variable+in+Windows, here are the steps:

1. Create a New System Variable, since, obviously, there isn't one (or else it would work?). In Windows, at least, it's under the Advanced tab of Properties.
2. New variable name JAVA_HOME with the path to the JRE, usually under "C:\Program Files (x86)\Java"
3. Once done, run the startup.bat (double click); a command prompt pops up and another window with Tomcat starts running.
4. Go to http://localhost:8888/ in browser, and viola, it runs!
   

[Dave Merrill]

Thanks for jumping in Chester, glad you got your system sorted. However, as noted above, for other reasons "I have Java 1.7 installed, and the system environment var JAVA_HOME points to it." I don't want to change the global environment var, that will affect other projects.

So:
- Where can I set JAVA_HOME in the Lucee scripts, so it affects only Lucee?
- The existing var points to a JDK. Will that work, or is a JRE is needed instead?
- Will Java 1.7 work, or is 1.8 required?

Thanks to anyone who can point me in some useful directions.

Dave

[Scott Busche]

Dave:

1: You can add a local variable at the top of the batch file as you suggested

set JAVA_HOME=/PathToJava1.8/

2: JDK has a JRE, so yes.

3: If changing to 1.8 causes the program to start, it would appear so, if it still doesn't work then continue debugging until it's working, once it is, switch back to 1.7 and see if it still works and report back. :)

[Dave Merrill]

To partially close the loop in this: After reading another thread about JRE_HOME, I set JRE_HOME to point to the JRE inside the same JDK 1.7 that the JAVA_HOME system var points to, and everything works now. Prior to that, I didn't get any errors or warnings mentioning JRE_HOME, just a dump .

I'm not sure if this is the right solution or not, given that Micha has said (I think) that something needs to be fixed for that build on Windows, but if you have htis issue and need to get running, it worked for me.

Dave

[Michael Offner]

Railo is working with Java 6 (1.6), 7 (1.7), 8 (1.8)

Micha

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/27704f4d-95a8-444d-9c31-793ead39a4ee%40googlegroups.com.

[Dave Merrill]

Micha, just to clarify, in this quote from you in the JDK_HOME thread: "I just did and we will improve that build asap. Problems seems only to happe n in windows", it seemed you were saying that people shouldn't need to set JDK_HOME like I did. I'm asking so other people with similar issues in the future who find this thread can know what to do.

My understanding as of now is that:
a) If you do have JAVA_HOME pointing to a valid JDK of a supported version and still have this problem, try setting JDK_HOME in startup.bat
b) There will be a new build at some point that will make that step unnecessary

Is that right?

Dave

[Igal @ Lucee.org]

yes, "Unsupported major.minor version 51.0" is a Java version.  51 is Java 7.

Lucee does not require Java 8 to run, no.

what do you see if you go to a command line and you run the following two commands:

    echo %JAVA_HOME%

    java -version

?

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/577801b5-7e60-4ec4-85a2-427dd114f8f2%40googlegroups.com.

[mmm mmm]

Windows users, after doing some checking on tomcat config files, all that's really needed is to edit the setclasspath.bat file in the lucee/bin directory,

rem ---------------------------------------------------------------------------

rem Set JAVA_HOME or JRE_HOME if not already set, ensure any provided settings

rem are valid and consistent with the selected start-up options and set up the

rem endorsed directory.

rem ---------------------------------------------------------------------------

set JRE_HOME=D:\Java\jdk1.7\jre

set JDK_HOME=D:\Java\jdk1.7

my JDK just happens to be on drive D so adjust accordingly--duh, 

if you install a jdk it also installs a jre--see above, sounds like tomcat uses the jre  if both are specified

it uses jdk for debugging? Seldom used?

So in other words you can use a jre that came with railo/jetty express, drop it wherever and point to it in the setclasspath.bat file

no need to set environment variables windows.

[Michael Offner]

Yes, the jetty version never needed that to define java_home, when Java is installed you simply can do "java ..." Because it is in the path.

Tomcat express has to learn that lesson, I'm also considering doing version that bundle the jre, that way the environment does not matter...

Am Mittwoch, 4. Februar 2015 schrieb Dave Merrill :

Micha, just to clarify, in this quote from you in the JDK_HOME thread: "I just did and we will improve that build asap. Problems seems only to happe n in windows", it seemed you were saying that people shouldn't need to set JDK_HOME like I did. I'm asking so other people with similar issues in the future who find this thread can know what to do.

My understanding as of now is that:
a) If you do have JAVA_HOME pointing to a valid JDK of a supported version and still have this problem, try setting JDK_HOME in startup.bat
b) There will be a new build at some point that will make that step unnecessary

Is that right?

Dave

On Wednesday, February 4, 2015 at 7:48:00 AM UTC-5, Micha wrote:

Railo is working with Java 6 (1.6), 7 (1.7), 8 (1.8)

Micha

Am Mittwoch, 4. Februar 2015 schrieb Dave Merrill :

To partially close the loop in this: After reading another thread about JRE_HOME, I set JRE_HOME to point to the JRE inside the same JDK 1.7 that the JAVA_HOME system var points to, and everything works now. Prior to that, I didn't get any errors or warnings mentioning JRE_HOME, just a dump .

I'm not sure if this is the right solution or not, given that Micha has said (I think) that something needs to be fixed for that build on Windows, but if you have htis issue and need to get running, it worked for me.

Dave

--

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/472e3ff4-1e20-4b04-8842-f90a4b3c5401%40googlegroups.com.

[Dave Merrill]

Thanks for jumping in Igal.

Echoing JAVA_HOME, it points to a Java 1.7 JDK, valid and used by multiple ACF and Railo instances on this box without problems. Java version reported is 1.7.0_75, which as I understand it is fine.

I'm sorry guys (not you specifically Igal), but these various responses are still totally unclear to me. On one level it doesn't matter to me, since I'm up and running after setting JDK_HOME in startup.bat and shutdown.bat, but in terms of making it clear to others with similar problems what they should do, we're not there yet.

To quote myself, this is my as-yet-unconfirmed-by-the-community hypothesis:

a) If you do have JAVA_HOME pointing to a valid JDK with a supported version and still have this problem, try setting JDK_HOME in startup.bat (and shutdown.bat)

b) There will be a new build at some point that will make that step unnecessary

Is that right?

I'm not trying to be difficult, or critical of anyone, just trying to leave clear, unambiguous info for anyone who just wants this to work.

Thanks,
Dave
 

[John Farrar]

Things sound amazing here. Struggles yes but awesome seems to be crawling from the results.

[mmm mmm]

Why did they switch from jetty to tomcat?

O.K. when you installed jdk did you also install the public jre? If so everything should have worked fine,
if you did not install the public jre there still is a jre in the jdk folder,
tomcat needs to be pointed to that jre, like I posted earlier which seems to be the correct way after checking with some tomcat forums.

http://www.codejava.net/servers/tomcat/4-ways-to-change-jre-for-tomcat

[Mark Drew]

Ease of support of one servlet engine vs another. Lots of clarifications always start with "what servlet engine are you running?"

Mark Drew

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/85cfb3c6-5eef-40e0-b9c0-b3c11df80c19%40googlegroups.com.

[Dave Merrill]

Yes, the JDK that the system JAVA_HOME var points to contains a JRE. I've also tried pointing JAVA_HOME directly at the jre dir, in startup.bat, no joy. Only thing that has worked so far is setting JRE_HOME to point there, in startup.bat.

Just to note, the system environment var JAVA_HOME already points to the same JDK, and works for other apps.

Dave

[Igal @ Lucee.org]

Dave,

maybe a clarification of the process will help.  it's all very simple stuff, really.

every Java Runtime Environment (JRE) ships with an executable program named "java" (e.g. java.exe in Windows).  in order to run a Java program, like Catalina in this case (which is the servlet container component of Tomcat, that in turn runs Lucee), you need to call the java executable and point to the java program's main entry point.  (a slight variation when running as a service, where you reference the jvm.dll as opposed to the java executable).

so now the paths come into play. 

most batch (and shell) scripts that ship with java programs don't know where the JRE/bin is installed, so it's become the standard way of using environment variables like JAVA_HOME (points to the JDK) and JRE_HOME (points to... well... the JRE).  then the script does something like that (pseudo-cfscript-code):

if (fileExists("#JRE_HOME#/bin/java.exe"))
    bin = "#JRE_HOME#/bin";
else if (fileExists("#JAVA_HOME#/jre/bin/java.exe"))
    bin = "#JAVA_HOME#/jre/bin";
else {

    echo("The JRE_HOME environment variable is not defined correctly. This environment variable is needed to run this program");
    abort;
}

execute "#bin#/java" args;

so in your case modifying the batch script and removing "directory" prefix before the "java" call would have been sufficient.

if we need to improve the scripts, we will do it as soon as possible once we find the problems (user reporting is the best way for us to find problems).

HTH,


Igal

p.s. if you have the JRE's bin directory in your system classpath, you can simply call "java", as you did when you tried "java -version" and got the JRE to report its version (if you hadn't had the bin directory in your system classpath you would have gotten an error).

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/f582db63-eb8f-4621-9484-5efa4d5a61e7%40googlegroups.com.

[Bob Dronski]

Another issue on another platform:

I was trying to use the express version on a macbook running 10.9.  After installing the current JRE, I tried to "just run" the startup.sh to no success.  I followed Mark's directions to get debug information and found this:

web1:bin bobd$ ./catalina.sh run

Using CATALINA_BASE:   /Users/bobd/downloads/lucee-4

Using CATALINA_HOME:   /Users/bobd/downloads/lucee-4

Using CATALINA_TMPDIR: /Users/bobd/downloads/lucee-4/temp

Using JRE_HOME:        /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home

Using CLASSPATH:       /Users/bobd/downloads/lucee-4/bin/bootstrap.jar:/Users/bobd/downloads/lucee-4/bin/tomcat-juli.jar

Exception in thread "main" java.lang.UnsupportedClassVersionError: org/apache/catalina/startup/Bootstrap : Unsupported major.minor version 51.0

at java.lang.ClassLoader.defineClass1(Native Method)

at java.lang.ClassLoader.defineClassCond(ClassLoader.java:637)

at java.lang.ClassLoader.defineClass(ClassLoader.java:621)

at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)

at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)

at java.net.URLClassLoader.access$000(URLClassLoader.java:58)

at java.net.URLClassLoader$1.run(URLClassLoader.java:197)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(URLClassLoader.java:190)

at java.lang.ClassLoader.loadClass(ClassLoader.java:306)

at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)

at java.lang.ClassLoader.loadClass(ClassLoader.java:247)

I've been spoiled by railo and was thrilled to do the lucee jar drop on my test server, but really wanted to have the server running on this machine.  I guess I can go back and find an OS X railo installer but would like to get things working and help to clarify things more.

bob

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/54D6AA9B.5080100%40lucee.org.

[Kai Koenig]

The issue is that your system is running a Java 6 JDK:

Using JRE_HOME:        /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home

But the Tomcat bootstrap application requires Java 7 (51.0 is Java 7):

Exception in thread "main" java.lang.UnsupportedClassVersionError: org/apache/catalina/startup/Bootstrap : Unsupported major.minor version 51.0

Easiest solution for your case would be to install Java 7 or 8 on your Mac and set JRE_HOME to the appropriate directory.

Cheers

Kai

[Bob Dronski]

Kai,

Thanks for the quick reply.  I hadn’t been concerned about the java version because I DID download and install the current java.  Even checking the java system pref reports I’m current at 8 r31.  But the JRE_HOME still shows 1.6.0.  Even tried manually exporting the variable with no luck.

Continuing the search for fixing the variable….

bob

--
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/B61CC47D-0251-4BBD-A4CB-548F16B10F26%40gmail.com.

[Sean Herrala]

export JRE_HOME="`/usr/libexec/java_home -v '1.8*'`"

[Bob Dronski]

Sean,

Thanks for the info. Unfortunately, it seems harder to get rid of/override java 6 in 10.9 than I figured. Tried following Oracle's Directions, but didn't seem to do enough. I will get back to this sometime, but had to give up and get some actual work done.

I'm glad the issue is not on the lucee side, that's for sure. Of course, this doesn't mean I won't stop hating dealing with Java configs on client machines!

bob

On Feb 7, 2015, at 9:15 PM, Sean Herrala <hok...@gmail.com> wrote:

> export JRE_HOME="`/usr/libexec/java_home -v '1.8*'`"
>

> --
> 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/8b8ac4c1-6aa3-4019-993f-f26f7a923344%40googlegroups.com.

[Margaret Phillips]

Bob, I too am having a horrible time getting Lucee to run on the Mac 10.9.5. I never had such a hard time getting anything else to run on the mac.

I have Java 8 installed but I am still getting the unsupported version issue error. When I run java -version it says 1.6.0-65. Is it possible to get this to run on a Mac or not?

[Andrew Dixon]

Hi Margaret,

I have Lucee, both Express and via Tomcat running on the Mac no problem at all. You say:

When I run java -version it says 1.6.0-65. 

Is that starting from the terminal without changing directory? If so then you still have an old Java version installed as well and the path is resolving first to v1.6. If I do this I get the following:

andrew$ java -version
java version "1.7.0_75"
Java(TM) SE Runtime Environment (build 1.7.0_75-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.75-b04, mixed mode)

If I use "whereis" to find java in the path I get:

andrew$ whereis java
/usr/bin/java 

Then looking at /usr/bin/java I see that it is a symbolic link:

andrew$ ll /usr/bin/java
lrwxr-xr-x  1 root  wheel  74  4 Dec 08:57 /usr/bin/java -> /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/java

Following that I find that in the "Versions" directory in the above path I have:

andrew$ ll /System/Library/Frameworks/JavaVM.framework/Versions/
total 64
lrwxr-xr-x  1 root  wheel   10  4 Dec 08:57 1.4 -> CurrentJDK
lrwxr-xr-x  1 root  wheel   10  4 Dec 08:57 1.4.2 -> CurrentJDK
lrwxr-xr-x  1 root  wheel   10  4 Dec 08:57 1.5 -> CurrentJDK
lrwxr-xr-x  1 root  wheel   10  4 Dec 08:57 1.5.0 -> CurrentJDK
lrwxr-xr-x  1 root  wheel   10  4 Dec 08:57 1.6 -> CurrentJDK
lrwxr-xr-x  1 root  wheel   10  4 Dec 08:57 1.6.0 -> CurrentJDK
drwxr-xr-x  8 root  wheel  272  4 Dec 08:57 A
lrwxr-xr-x  1 root  wheel    1  4 Dec 08:57 Current -> A
lrwxr-xr-x  1 root  wheel   59  4 Dec 08:57 CurrentJDK -> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents

And that the "Current" directory is symlinked to "A" and in "A" (no idea why it is "A") is version 1.7.x.

Check this and I assume you will find that somewhere in those symlinks you are still linking to 1.6. Change the symlink and it should then work for you.

Kind regards,

Andrew

about.me
mso - Lucee - Member

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/0c443e1b-68b1-47d1-889a-45ba18d41da9%40googlegroups.com.

[Jon Clausen]

Margaret,

Since I run both ACF and Lucee on my Mac, I use the CommandBox embedded server and reverse-proxying through Apache when I need to test against Railo/Lucee (or you can use standalone).

If you want to save yourself some hassle, install CommandBox (https://github.com/Ortus-Solutions/commandbox ), grab the Lucee 4.5 jars ( http://bitbucket.org/lucee/lucee/downloads/lucee–4.5.1.000-jars.zip ) and drop them in ~/.CommandBox/lib/. From the root of your project run box server start and you’ll be running Lucee (I know Luis has a ticket open convert everything to Lucee from Railo, but I don’t know, as of this posting, if he’s gotten around to updating that yet).

I’m on OS X 10.0 now, but used this method on Mavericks and everything in the upgrade transferred just fine.

If you need to use different Java versions, you can use jEnv and Homebrew to do so very effectively (http://andrew-jones.com/blog/managing-multiple-versions-of-java-on-os-x/ )

Jon

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/0c443e1b-68b1-47d1-889a-45ba18d41da9%40googlegroups.com.

[denstar]

There is also this:

http://cfmlprojects.org/artifacts/org/lucee/lucee.tomcat.modcfml.jre/4.5.1.008/

(You'd want the Darwin zip)

The lucee-ctl script should even let you install it as a service, if you
want it to automatically have it start.

It's not the latest, but you could update through the admin.

I've set up all the bundles so that changing the JRE/JDK used is
straight forward (either move it to the JRE dir or remove the JRE dir
and use an environment variable), since that's kind of been an issue on
OS X and Windows.

There's also a version of lucee-cli which is set up to be an "express"
server:

http://cfmlprojects.org/artifacts/org/lucee/lucee.cli.express/1.0.0.4.5.1.008/

Micha had asked about a different way of doing "express"-- I like this
approach, it's definitely different. :)

When I get a chance I'll update things again for 5, and make another
push for getting the totes awesome build scripts incorporated-- it's
just going to take some coordination, and I've been busy.

-Den

[Eois McRae]

Hello
I was using Railo and am moving to Lucee.
Railo express - I unzipped and clicked on start.bat and it worked. No need to change edit fix.
Is there a Lucee express like that?
I want to check compatible issues, not become installer wizard.
Thank you.
E

[Jon Clausen]

The express version doesn’t work for you?  http://lucee.org/downloads.html

You can also check out CommandBox, which runs Lucee by default: https://www.ortussolutions.com/products/commandbox

--
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/0f1fb5d6-f849-4249-8626-adc236e62cdc%40googlegroups.com.

[Eois McRae]

Hello,
No, the express version doesn't work for me. I download it, unzip it, click on startup.bat, a command window opens and closes quickly and lucee isn't up and running.
CommandBox worked and I haven't explored running CFML through it yet.
I'd prefer just a Lucee express that works like Railo did, click and go.
E

[Mark Drew]

Try running the .bat file from the  the command line in windows rather than just double clicking it. IT should then give you a verbose error rather than just closing the window.


Eois McRae wrote:

Hello,
No, the express version doesn't work for me. I download it, unzip it,
click on startup.bat, a command window opens and closes quickly and
lucee isn't up and running.
CommandBox worked and I haven't explored running CFML through it yet.
I'd prefer just a Lucee express that works like Railo did, click and go.
E

On Friday, July 24, 2015 at 4:11:02 PM UTC-4, Jon Clausen wrote:

    The express version doesn’t work for you?
    http://lucee.org/downloads.html

    <http://lucee.org/downloads.html>

    <http://lucee.org/downloads.html>
    You can also check out CommandBox, which runs Lucee by default:
    https://www.ortussolutions.com/products/commandbox
    <https://www.ortussolutions.com/products/commandbox>

    On July 24, 2015 at 3:38:23 PM, Eois McRae

    (eo...@nextstagevolution.com <javascript:>) wrote:

    Hello
    I was using Railo and am moving to Lucee.
    Railo express - I unzipped and clicked on start.bat and it
    worked. No need to change edit fix.
    Is there a Lucee express like that?
    I want to check compatible issues, not become installer wizard.
    Thank you.
    E
    --
    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 <javascript:>.

    To post to this group, send email to lu...@googlegroups.com

    <javascript:>.

    To view this discussion on the web visit
    https://groups.google.com/d/msgid/lucee/0f1fb5d6-f849-4249-8626-adc236e62cdc%40googlegroups.com

    <https://groups.google.com/d/msgid/lucee/0f1fb5d6-f849-4249-8626-adc236e62cdc%40googlegroups.com?utm_medium=email&utm_source=footer>.

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

    <https://groups.google.com/d/optout>.

--
See Lucee at CFCamp Oct 22 & 23 2015 @ Munich Airport, Germany - Get
your ticket NOW - http://www.cfcamp.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

<mailto:lucee+un...@googlegroups.com>.

To post to this group, send email to lu...@googlegroups.com

<mailto:lu...@googlegroups.com>.

To view this discussion on the web visit

https://groups.google.com/d/msgid/lucee/bf43792a-21f6-4330-93c7-2b485e86755d%40googlegroups.com
<https://groups.google.com/d/msgid/lucee/bf43792a-21f6-4330-93c7-2b485e86755d%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Gert Franz]

The issue mostly is, that the JRE_HOME or JAVA_HOME isn't correctly set our defined in the batch.

Gert

Sent from somewhere on the road

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/55D35418.9000105%40gmail.com.

[Zac Spitzer]

have you got IIS installed? lucee (did) assume c:\inetpub\wwwwroot exists

<mailto:lucee...@googlegroups.com>.

To post to this group, send email to lu...@googlegroups.com

<mailto...@googlegroups.com>.

[Mark Drew]

Express doesn't need that path. 

Mark Drew

- Sent by typing with my thumbs. 

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/90c1d023-3dcf-45a4-9387-a98a7912b7c0%40googlegroups.com.

[Rob Langlands]

Hi.
I just downloaded Lucee Express for the first time today and got same problem when selecting startup.bat. I've been using Railo since.
I ran it from Command window & got the "Neither the JAVA_HOME nor the JRE_HOME environment variable is defined.

I did set the variables in the setclasspath.bat file, and works fine now.

This is just a heads up, as I assumed this error/problem would have been updated/fixed from August discussion.
Because if there's anyone NEW to Lucee trying the Express edition, immediate frustration may set in. It took me a while to search for this solution. If this can't be set properly on setup, maybe a Note for setup needs to be included in the download.

Thanks,
Rob

On 15-08-18 6:21 PM, Gert Franz wrote:

[Brad Wood]

Please run the following from a DOS window and report your output:

C:\>echo %JAVA_HOME%

C:\>echo %JRE_HOME%

Thanks!

~Brad

[Rob Langlands]

It just echoed the variable name. I see what you're getting at.
So, when the JDK is installed, those variables should have been set?
Looks like they were not on my system.

Rob

[Brad Wood]

Yep, if those environment variables aren't set then Tomcat can't start, so in a way it's behaving exactly as it should-- telling you it doesn't know how to run.  Now, if Railo express worked on the same system, I'm not sure what env variables it used or perhaps it bundled its own JRE.  At one point I thought the Lucee Express version was exactly the same as Railo's but now I'm thinking Railo might have been on Jetty.  

Thanks!

~Brad

ColdBox Platform Evangelist

Ortus Solutions, Corp 

E-mail: br...@coldbox.org

ColdBox Platform: http://www.coldbox.org 

Blog: http://www.codersrevolution.com