Lucee 5 on Jetty 9.3.x

I removed all of the Jars per the upgrade from 4.5 to 5.x. That did not go
well. I deleted off the Lucee-server folder. The system sort of came up
and I was able to get into the Server Admin.

The folder structure created is

lucee-server / lucee-server / bundles
lucee-server / lucee-server / context
lucee-server / lucee-server / deploy
lucee-server / lucee-server / felix-cache
lucee-server / lucee-server / patches

The nested lucee-server seems strange.

Then when I restart the server I get these errors.

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/C:/Servers/lucee-5-JettyBase/lib/ext/lucee-server/lucee-server/bundles/slf4j.nop-1.7.12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/C:/Servers/lucee-5-JettyBase/lib/ext/lucee-server/lucee-server/felix-cache/bundle63/version0.0/bundle.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
SLF4J: Actual binding is of type [org.slf4j.helpers.NOPLoggerFactory]

– System –

Windows 10 Pro 64 Bit
Java 1.8.0_77
Jetty 9.3.8
Lucee 5.0.0.235 - latest available from the download page. Lucee with

Andrew Penhorwood

check https://github.com/boughtonp/lucee-on-jetty?On Tuesday, April 19, 2016 at 3:37:37 PM UTC-4, Andrew Penhorwood wrote:

Does anyone have Lucee 5.x running on Jetty 9.3.x?

Andrew Penhorwood

On Tuesday, April 19, 2016 at 6:24:47 AM UTC-4, Andrew Penhorwood wrote:

I removed all of the Jars per the upgrade from 4.5 to 5.x. That did not
go well. I deleted off the Lucee-server folder. The system sort of came
up and I was able to get into the Server Admin.

The folder structure created is

lucee-server / lucee-server / bundles
lucee-server / lucee-server / context
lucee-server / lucee-server / deploy
lucee-server / lucee-server / felix-cache
lucee-server / lucee-server / patches

The nested lucee-server seems strange.

Then when I restart the server I get these errors.

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/C:/Servers/lucee-5-JettyBase/lib/ext/lucee-server/lucee-server/bundles/slf4j.nop-1.7.12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/C:/Servers/lucee-5-JettyBase/lib/ext/lucee-server/lucee-server/felix-cache/bundle63/version0.0/bundle.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
SLF4J: Actual binding is of type [org.slf4j.helpers.NOPLoggerFactory]

– System –

Windows 10 Pro 64 Bit
Java 1.8.0_77
Jetty 9.3.8
Lucee 5.0.0.235 - latest available from the download page. Lucee with

Andrew Penhorwood

Does anyone have Lucee 5.x running on Jetty 9.3.x?

Andrew PenhorwoodOn Tuesday, April 19, 2016 at 6:24:47 AM UTC-4, Andrew Penhorwood wrote:

I removed all of the Jars per the upgrade from 4.5 to 5.x. That did not
go well. I deleted off the Lucee-server folder. The system sort of came
up and I was able to get into the Server Admin.

The folder structure created is

lucee-server / lucee-server / bundles
lucee-server / lucee-server / context
lucee-server / lucee-server / deploy
lucee-server / lucee-server / felix-cache
lucee-server / lucee-server / patches

The nested lucee-server seems strange.

Then when I restart the server I get these errors.

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/C:/Servers/lucee-5-JettyBase/lib/ext/lucee-server/lucee-server/bundles/slf4j.nop-1.7.12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/C:/Servers/lucee-5-JettyBase/lib/ext/lucee-server/lucee-server/felix-cache/bundle63/version0.0/bundle.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
SLF4J: Actual binding is of type [org.slf4j.helpers.NOPLoggerFactory]

– System –

Windows 10 Pro 64 Bit
Java 1.8.0_77
Jetty 9.3.8
Lucee 5.0.0.235 - latest available from the download page. Lucee with

Andrew Penhorwood

Looks like it is very easy to upgrade from Lucee 4.5->5

  1. remove all files in lucee-base/lib/ext directory
  2. put lucee-5.0.0.235-RC.jar there (lucee-base/lib/ext)
  3. remove all files in lucee-base/lucee-server directory
  4. exec start-server.bat (in windows)
  5. http://localhost:8080/

you can also replace jetty to be the latest versionOn Tuesday, April 19, 2016 at 4:48:13 PM UTC-4, Allen Weng wrote:

check https://github.com/boughtonp/lucee-on-jetty?

On Tuesday, April 19, 2016 at 3:37:37 PM UTC-4, Andrew Penhorwood wrote:

Does anyone have Lucee 5.x running on Jetty 9.3.x?

Andrew Penhorwood

On Tuesday, April 19, 2016 at 6:24:47 AM UTC-4, Andrew Penhorwood wrote:

I removed all of the Jars per the upgrade from 4.5 to 5.x. That did not
go well. I deleted off the Lucee-server folder. The system sort of came
up and I was able to get into the Server Admin.

The folder structure created is

lucee-server / lucee-server / bundles
lucee-server / lucee-server / context
lucee-server / lucee-server / deploy
lucee-server / lucee-server / felix-cache
lucee-server / lucee-server / patches

The nested lucee-server seems strange.

Then when I restart the server I get these errors.

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/C:/Servers/lucee-5-JettyBase/lib/ext/lucee-server/lucee-server/bundles/slf4j.nop-1.7.12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/C:/Servers/lucee-5-JettyBase/lib/ext/lucee-server/lucee-server/felix-cache/bundle63/version0.0/bundle.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
SLF4J: Actual binding is of type [org.slf4j.helpers.NOPLoggerFactory]

– System –

Windows 10 Pro 64 Bit
Java 1.8.0_77
Jetty 9.3.8
Lucee 5.0.0.235 - latest available from the download page. Lucee with

Andrew Penhorwood

Hi, Andrew

Actually, I missed one folder to be included in the previous post… here
is the updated steps

  1. get the Lucee 4.5 + Jetty 9 from
    https://github.com/boughtonp/lucee-on-jetty
  2. remove all files in lucee-base/lib/ext directory
  3. put lucee-5.0.0.235-RC.jar there (lucee-base/lib/ext)
  4. remove all files in lucee-base/lucee-server and lucee-base/webinfs
    directories
  5. exec start-server.bat (in windows)
  6. http://localhost:8080/On Tuesday, April 19, 2016 at 9:28:39 PM UTC-4, Andrew Penhorwood wrote:

Thanks for your post. I am comparing your Jetty files to mine to see how
we differ.

Andrew Penhorwood

On Tuesday, April 19, 2016 at 5:12:28 PM UTC-4, Allen Weng wrote:

Looks like it is very easy to upgrade from Lucee 4.5->5

  1. remove all files in lucee-base/lib/ext directory
  2. put lucee-5.0.0.235-RC.jar there (lucee-base/lib/ext)
  3. remove all files in lucee-base/lucee-server directory
  4. exec start-server.bat (in windows)
  5. http://localhost:8080/

you can also replace jetty to be the latest version

On Tuesday, April 19, 2016 at 4:48:13 PM UTC-4, Allen Weng wrote:

check https://github.com/boughtonp/lucee-on-jetty?

On Tuesday, April 19, 2016 at 3:37:37 PM UTC-4, Andrew Penhorwood wrote:

Does anyone have Lucee 5.x running on Jetty 9.3.x?

Andrew Penhorwood

On Tuesday, April 19, 2016 at 6:24:47 AM UTC-4, Andrew Penhorwood wrote:

I removed all of the Jars per the upgrade from 4.5 to 5.x. That did
not go well. I deleted off the Lucee-server folder. The system sort of
came up and I was able to get into the Server Admin.

The folder structure created is

lucee-server / lucee-server / bundles
lucee-server / lucee-server / context
lucee-server / lucee-server / deploy
lucee-server / lucee-server / felix-cache
lucee-server / lucee-server / patches

The nested lucee-server seems strange.

Then when I restart the server I get these errors.

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/C:/Servers/lucee-5-JettyBase/lib/ext/lucee-server/lucee-server/bundles/slf4j.nop-1.7.12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/C:/Servers/lucee-5-JettyBase/lib/ext/lucee-server/lucee-server/felix-cache/bundle63/version0.0/bundle.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
SLF4J: Actual binding is of type [org.slf4j.helpers.NOPLoggerFactory]

– System –

Windows 10 Pro 64 Bit
Java 1.8.0_77
Jetty 9.3.8
Lucee 5.0.0.235 - latest available from the download page. Lucee with

Andrew Penhorwood

I did all of that and as soon as I stop and restart Jetty I get these
errors.

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/C:/Servers/lucee-5-JettyBase/lib/ext/lucee-server/lucee-server/bundles/slf4j.nop-1.7.12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/C:/Servers/lucee-5-JettyBase/lib/ext/lucee-server/lucee-server/felix-cache/bundle63/version0.0/bundle.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
SLF4J: Actual binding is of type [org.slf4j.helpers.NOPLoggerFactory]

I am not new to Jetty. I have been using on Windows and Linux for years.
The Jetty installation is basically stock. The only changes were to
Webdefault.xml which removed the JSP servlet and added the Lucee servlet.
The start.ini file is basic stuff to get the Lucee up and running. Not
much to look at.

I first upgraded to the 4.5 to 5.0 by removing the Jar files. That worked
but the restart had issues. So I removed the lucee-server folder since
this is a test machine. (The configuration could be redone).

Andrew PenhorwoodOn Tuesday, April 19, 2016 at 5:12:28 PM UTC-4, Allen Weng wrote:

Looks like it is very easy to upgrade from Lucee 4.5->5

  1. remove all files in lucee-base/lib/ext directory
  2. put lucee-5.0.0.235-RC.jar there (lucee-base/lib/ext)
  3. remove all files in lucee-base/lucee-server directory
  4. exec start-server.bat (in windows)
  5. http://localhost:8080/

you can also replace jetty to be the latest version

On Tuesday, April 19, 2016 at 4:48:13 PM UTC-4, Allen Weng wrote:

check https://github.com/boughtonp/lucee-on-jetty?

On Tuesday, April 19, 2016 at 3:37:37 PM UTC-4, Andrew Penhorwood wrote:

Does anyone have Lucee 5.x running on Jetty 9.3.x?

Andrew Penhorwood

On Tuesday, April 19, 2016 at 6:24:47 AM UTC-4, Andrew Penhorwood wrote:

I removed all of the Jars per the upgrade from 4.5 to 5.x. That did
not go well. I deleted off the Lucee-server folder. The system sort of
came up and I was able to get into the Server Admin.

The folder structure created is

lucee-server / lucee-server / bundles
lucee-server / lucee-server / context
lucee-server / lucee-server / deploy
lucee-server / lucee-server / felix-cache
lucee-server / lucee-server / patches

The nested lucee-server seems strange.

Then when I restart the server I get these errors.

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/C:/Servers/lucee-5-JettyBase/lib/ext/lucee-server/lucee-server/bundles/slf4j.nop-1.7.12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/C:/Servers/lucee-5-JettyBase/lib/ext/lucee-server/lucee-server/felix-cache/bundle63/version0.0/bundle.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
SLF4J: Actual binding is of type [org.slf4j.helpers.NOPLoggerFactory]

– System –

Windows 10 Pro 64 Bit
Java 1.8.0_77
Jetty 9.3.8
Lucee 5.0.0.235 - latest available from the download page. Lucee with

Andrew Penhorwood

I’m surprised this method actually works… you can restart without
issue too?

FWIW, for a stock jetty 9.3.8, I had to add this to webdefault.xml:

org.eclipse.jetty.jsp.precompiled true

To prevent the TLD scanning of a default Lucee 5 war deployed in
webapps/root

Otherwise, it would start fine the first time, but choke on subsequent
starts when it found the TLD files extracted on that first run.

Oh, wait a second-- I bet why the below route works is because it
extracts the context files to a non-default directory, thus avoiding the
scan altogether. Yep, bet that’s it. Sounds plausible at least.

DeNOn 04/19/2016 08:56 PM, Allen Weng wrote:

Hi, Andrew

Actually, I missed one folder to be included in the previous post…
here is the updated steps

  1. get the Lucee 4.5 + Jetty 9 from
    https://github.com/boughtonp/lucee-on-jetty
  2. remove all files in lucee-base/lib/ext directory
  3. put lucee-5.0.0.235-RC.jar there (lucee-base/lib/ext)
  4. remove all files in lucee-base/lucee-server and lucee-base/webinfs
    directories
  5. exec start-server.bat (in windows)
  6. http://localhost:8080/

I got one context to work last night. I hope to reproduce the original
sf4j issue later in the week. I believe that had to do with the logger I
had defined. This morning I tried adding a 2nd context and only one
context started correctly. I will try to look into that more after work
tonight. The day job is a ACF 10 adventure.

@Allen - Thanks again for sharing your configuration. I see that you
created a lucee.mod file. Most of my config lives in the start.ini file.
I also put the lucee servlet stuff directly in the webdefault.xml file.

Andrew PenhorwoodOn Wednesday, April 20, 2016 at 2:13:48 AM UTC-4, Denny Valliant wrote:

I’m surprised this method actually works… you can restart without
issue too?

FWIW, for a stock jetty 9.3.8, I had to add this to webdefault.xml:

org.eclipse.jetty.jsp.precompiled true

To prevent the TLD scanning of a default Lucee 5 war deployed in
webapps/root

Otherwise, it would start fine the first time, but choke on subsequent
starts when it found the TLD files extracted on that first run.

Oh, wait a second-- I bet why the below route works is because it
extracts the context files to a non-default directory, thus avoiding the
scan altogether. Yep, bet that’s it. Sounds plausible at least.

DeN

On 04/19/2016 08:56 PM, Allen Weng wrote:

Hi, Andrew

Actually, I missed one folder to be included in the previous post…
here is the updated steps

  1. get the Lucee 4.5 + Jetty 9 from
    https://github.com/boughtonp/lucee-on-jetty
  2. remove all files in lucee-base/lib/ext directory
  3. put lucee-5.0.0.235-RC.jar there (lucee-base/lib/ext)
  4. remove all files in lucee-base/lucee-server and lucee-base/webinfs
    directories
  5. exec start-server.bat (in windows)
  6. http://localhost:8080/

Thanks for your post. I am comparing your Jetty files to mine to see how
we differ.

Andrew PenhorwoodOn Tuesday, April 19, 2016 at 5:12:28 PM UTC-4, Allen Weng wrote:

Looks like it is very easy to upgrade from Lucee 4.5->5

  1. remove all files in lucee-base/lib/ext directory
  2. put lucee-5.0.0.235-RC.jar there (lucee-base/lib/ext)
  3. remove all files in lucee-base/lucee-server directory
  4. exec start-server.bat (in windows)
  5. http://localhost:8080/

you can also replace jetty to be the latest version

On Tuesday, April 19, 2016 at 4:48:13 PM UTC-4, Allen Weng wrote:

check https://github.com/boughtonp/lucee-on-jetty?

On Tuesday, April 19, 2016 at 3:37:37 PM UTC-4, Andrew Penhorwood wrote:

Does anyone have Lucee 5.x running on Jetty 9.3.x?

Andrew Penhorwood

On Tuesday, April 19, 2016 at 6:24:47 AM UTC-4, Andrew Penhorwood wrote:

I removed all of the Jars per the upgrade from 4.5 to 5.x. That did
not go well. I deleted off the Lucee-server folder. The system sort of
came up and I was able to get into the Server Admin.

The folder structure created is

lucee-server / lucee-server / bundles
lucee-server / lucee-server / context
lucee-server / lucee-server / deploy
lucee-server / lucee-server / felix-cache
lucee-server / lucee-server / patches

The nested lucee-server seems strange.

Then when I restart the server I get these errors.

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/C:/Servers/lucee-5-JettyBase/lib/ext/lucee-server/lucee-server/bundles/slf4j.nop-1.7.12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/C:/Servers/lucee-5-JettyBase/lib/ext/lucee-server/lucee-server/felix-cache/bundle63/version0.0/bundle.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.
SLF4J: Actual binding is of type [org.slf4j.helpers.NOPLoggerFactory]

– System –

Windows 10 Pro 64 Bit
Java 1.8.0_77
Jetty 9.3.8
Lucee 5.0.0.235 - latest available from the download page. Lucee with

Andrew Penhorwood

@Denny

On Allen’s setup he is doing most of the work in the lucee.mod file. His
config does not use deploy but he is adding the lucee files as a lib in the
lucee.mod file. Not real sure how all of that works.

Andrew PenhorwoodOn Wednesday, April 20, 2016 at 2:13:48 AM UTC-4, Denny Valliant wrote:

I’m surprised this method actually works… you can restart without
issue too?

FWIW, for a stock jetty 9.3.8, I had to add this to webdefault.xml:

org.eclipse.jetty.jsp.precompiled true

To prevent the TLD scanning of a default Lucee 5 war deployed in
webapps/root

Otherwise, it would start fine the first time, but choke on subsequent
starts when it found the TLD files extracted on that first run.

Oh, wait a second-- I bet why the below route works is because it
extracts the context files to a non-default directory, thus avoiding the
scan altogether. Yep, bet that’s it. Sounds plausible at least.

DeN

On 04/19/2016 08:56 PM, Allen Weng wrote:

Hi, Andrew

Actually, I missed one folder to be included in the previous post…
here is the updated steps

  1. get the Lucee 4.5 + Jetty 9 from
    https://github.com/boughtonp/lucee-on-jetty
  2. remove all files in lucee-base/lib/ext directory
  3. put lucee-5.0.0.235-RC.jar there (lucee-base/lib/ext)
  4. remove all files in lucee-base/lucee-server and lucee-base/webinfs
    directories
  5. exec start-server.bat (in windows)
  6. http://localhost:8080/