Lucee.war on vanilla Tomcat install

dev google-group-archive
1

G’day:
Whilst troubleshooting an issue that might exist in the Lucee express
install, I decided to try the WAR install instead. I will hasten to add my
knowledge / degree-of-comfort with Tomcat is minimal, but I can follow
instructions (if they’re available to find, that is).

I’ve done this:

  1. D/L the Windows 64-bit version of Tomcat 8 from their site
  2. unzip it into C:\apps\apache\tomcat\8. This is the first and only
    install of Tomcat on this computer
  3. create a setenv.bat file in the bin subdirectory of the above. This sets
    CATALINA_HOME to the directory above, and for good measure set JAVA_HOME to
    point to where my Java 8 JDK is installed.
  4. I add a user to the tomcat-users.xml file so I can access the app
    manager GUI.
  5. I start Tomcat with startup.bat. It starts A-OK. I can access the app
    manager GUI too. Everything is all-present and correct as far as my
    understanding of things goes.
  6. I stop Tomcat
  7. I D/L the latest (5.0.0.45) Lucee WAR file.
  8. I put it in Tomcat’s webapps subdir, and rename it as just lucee.war
  9. I start Tomcat. I see it deploying Lucee
  10. I return to the app manager UI, and see that Lucee is not running. I
    opt to start it.
  11. I get an error that it failed to start in the status area @ the top of
    the screen.
  12. consulting the catalina-out log, I see this lot:

30-Apr-2015 08:33:50.084 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Deploying web application
archive C:\apps\apache\tomcat\8\webapps\lucee.war
30-Apr-2015 08:33:50.410 SEVERE [localhost-startStop-1]
org.apache.catalina.core.ContainerBase.addChildInternal
ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/lucee]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:940)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1738)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.SecurityException: no manifiest section for signature
file entry org/bouncycastle/jce/provider/JDKMessageDigest$RIPEMD256.class
at
sun.security.util.SignatureFileVerifier.verifySection(SignatureFileVerifier.java:440)
at
sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:295)
at
sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:238)
at java.util.jar.JarVerifier.processEntry(JarVerifier.java:316)
at java.util.jar.JarVerifier.update(JarVerifier.java:228)
at java.util.jar.JarFile.initializeVerifier(JarFile.java:383)
at java.util.jar.JarFile.getInputStream(JarFile.java:450)
at
org.apache.catalina.webresources.JarResource.getJarInputStreamWrapper(JarResource.java:46)
at
org.apache.catalina.webresources.AbstractArchiveResource.doGetInputStream(AbstractArchiveResource.java:218)
at
org.apache.catalina.webresources.AbstractResource.getInputStream(AbstractResource.java:94)
at
org.apache.catalina.util.ExtensionValidator.validateApplication(ExtensionValidator.java:152)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4992)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
… 10 more

30-Apr-2015 08:33:50.414 SEVERE [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Error deploying web
application archive C:\apps\apache\tomcat\8\webapps\lucee.war
java.lang.IllegalStateException: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/lucee]]
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:728)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:940)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1738)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

30-Apr-2015 08:33:50.419 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Deployment of web
application archive C:\apps\apache\tomcat\8\webapps\lucee.war has finished
in 334 ms

I have highlighted the bit I suspect is a problem.

I have experienced the following issue on two machines: one running Windows
7 64-bit, and one running Windows 8.1 64-bit.

Questions:

  1. have I done something wrong? I could find no docs saying that to deploy
    Lucee as a WAR I have to do anything other than the default approach, and
    my understanding is “drop the WAR file into the webapps dir and start
    Tomcat” is all that’s required for that.
  2. Do I need to configure something for this library to work?
  3. Is there a problem with the WAR file?

I’m erring towards me doing something wrong, but not sure what to do about
working out what, other than asking here. I looked for other threads here
with ppl having similar issues, and also consulted the wiki, but found
nothing relevant.

Cheers.–
Adam

2

Adam,

I use a similar approach on my development boxes, so I tried deploying the
current Lucee 5 WAR on both Tomcat 7.0.61 and Tomcat 8.0.21 on one of my
boxes. In both cases, I use a Host stanza like the following to do the
initial deploy of the WAR (but not start it):



And then use something like the following to start Tomcat:

$ CATALINA_BASE=. ~/opt/ron/t7/bin/startup.sh

or

$ CATALINA_BASE=.~/opt/ron/t8/bin/startup.sh

On both Tomcat 8 and Tomcat 7, I get errors very similar to yours in just
deploying the context, so it seems like either there’s a problem with the
WAR or there is something else needed in order to deploy successfully.

My ./logs/catalina.out for the Tomcat8 instance shows:

01-May-2015 05:30:54.547 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server version:
Apache Tomcat/8.0.21
01-May-2015 05:30:54.559 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server built:
Mar 23 2015 14:11:21 UTC
01-May-2015 05:30:54.559 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Server number:
8.0.21.0
01-May-2015 05:30:54.560 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log OS Name:
Mac OS X
01-May-2015 05:30:54.560 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log OS Version:
10.10.3
01-May-2015 05:30:54.560 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Architecture:
x86_64
01-May-2015 05:30:54.560 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Java Home:
/Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home/jre
01-May-2015 05:30:54.560 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log JVM Version:
1.8.0_45-b14
01-May-2015 05:30:54.560 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:
Oracle Corporation
01-May-2015 05:30:54.560 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:
/Users/ron/opt/t8i/l5
01-May-2015 05:30:54.560 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:
/Users/ron/opt/t8
01-May-2015 05:30:54.561 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Djava.util.logging.config.file=./conf/logging.properties
01-May-2015 05:30:54.561 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
01-May-2015 05:30:54.561 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Djava.endorsed.dirs=/Users/ron/opt/t8/endorsed
01-May-2015 05:30:54.561 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Dcatalina.base=.
01-May-2015 05:30:54.561 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Dcatalina.home=/Users/ron/opt/t8
01-May-2015 05:30:54.562 INFO [main]
org.apache.catalina.startup.VersionLoggerListener.log Command line
argument: -Djava.io.tmpdir=./temp
01-May-2015 05:30:54.562 INFO [main]
org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based
Apache Tomcat Native library which allows optimal performance in production
environments was not found on the java.library.path:
/Users/ron/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.
01-May-2015 05:30:55.389 INFO [main]
org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
[“http-nio-8080”]
01-May-2015 05:30:55.533 INFO [main]
org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared
selector for servlet write/read
01-May-2015 05:30:55.538 INFO [main]
org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
[“ajp-nio-8009”]
01-May-2015 05:30:55.541 INFO [main]
org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared
selector for servlet write/read
01-May-2015 05:30:55.542 INFO [main]
org.apache.catalina.startup.Catalina.load Initialization processed in 2706
ms
01-May-2015 05:30:55.599 INFO [main]
org.apache.catalina.core.StandardService.startInternal Starting service
Catalina
01-May-2015 05:30:55.600 INFO [main]
org.apache.catalina.core.StandardEngine.startInternal Starting Servlet
Engine: Apache Tomcat/8.0.21
01-May-2015 05:30:57.350 SEVERE [Catalina-startStop-1]
org.apache.catalina.core.ContainerBase.startInternal A child container
failed during start
java.util.concurrent.ExecutionException:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext]
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:917)
at
org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:871)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1409)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1399)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.catalina.LifecycleException: Failed to start
component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
… 6 more
Caused by: java.lang.SecurityException: no manifiest section for signature
file entry org/bouncycastle/jce/provider/JDKMessageDigest$RIPEMD256.class
at
sun.security.util.SignatureFileVerifier.verifySection(SignatureFileVerifier.java:440)
at
sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:295)
at
sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:238)
at java.util.jar.JarVerifier.processEntry(JarVerifier.java:316)
at java.util.jar.JarVerifier.update(JarVerifier.java:228)
at java.util.jar.JarFile.initializeVerifier(JarFile.java:383)
at java.util.jar.JarFile.getInputStream(JarFile.java:450)
at
org.apache.catalina.webresources.JarResource.getJarInputStreamWrapper(JarResource.java:46)
at
org.apache.catalina.webresources.AbstractArchiveResource.doGetInputStream(AbstractArchiveResource.java:218)
at
org.apache.catalina.webresources.AbstractResource.getInputStream(AbstractResource.java:94)
at
org.apache.catalina.util.ExtensionValidator.validateApplication(ExtensionValidator.java:152)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4992)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
… 6 more

01-May-2015 05:30:57.358 SEVERE [main]
org.apache.catalina.core.ContainerBase.startInternal A child container
failed during start
java.util.concurrent.ExecutionException:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost]]
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:917)
at
org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.StandardService.startInternal(StandardService.java:439)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:769)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.startup.Catalina.start(Catalina.java:625)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:351)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:485)
Caused by: org.apache.catalina.LifecycleException: Failed to start
component [StandardEngine[Catalina].StandardHost[localhost]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1409)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1399)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.catalina.LifecycleException: A child container failed
during start
at
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:925)
at
org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:871)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
… 6 more

01-May-2015 05:30:57.359 SEVERE [main]
org.apache.catalina.startup.Catalina.start The required Server component
failed to start so Tomcat is unable to start.
org.apache.catalina.LifecycleException: Failed to start component
[StandardServer[8005]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at org.apache.catalina.startup.Catalina.start(Catalina.java:625)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:351)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:485)
Caused by: org.apache.catalina.LifecycleException: Failed to start
component [StandardService[Catalina]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at
org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:769)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
… 7 more
Caused by: org.apache.catalina.LifecycleException: Failed to start
component [StandardEngine[Catalina]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at
org.apache.catalina.core.StandardService.startInternal(StandardService.java:439)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
… 9 more
Caused by: org.apache.catalina.LifecycleException: A child container failed
during start
at
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:925)
at
org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
… 11 more

My ./catalina.out for the Tomcat 7 instance shows:

May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Server version: Apache Tomcat/7.0.61
May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Server built: Mar 27 2015 12:03:56 UTC
May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Server number: 7.0.61.0
May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: OS Name: Mac OS X
May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: OS Version: 10.10.3
May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Architecture: x86_64
May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Java Home:
/Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home/jre
May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: JVM Version: 1.8.0_45-b14
May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: JVM Vendor: Oracle Corporation
May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: CATALINA_BASE: /Users/ron/opt/t7i/l5
May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: CATALINA_HOME: /Users/ron/opt/t7
May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument:
-Djava.util.logging.config.file=./conf/logging.properties
May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument:
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument: -Djava.endorsed.dirs=/Users/ron/opt/t7/endorsed
May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument: -Dcatalina.base=.
May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument: -Dcatalina.home=/Users/ron/opt/t7
May 01, 2015 5:44:20 AM org.apache.catalina.startup.VersionLoggerListener
log
INFO: Command line argument: -Djava.io.tmpdir=./temp
May 01, 2015 5:44:20 AM org.apache.catalina.core.AprLifecycleListener
lifecycleEvent
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path:
/Users/ron/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.
May 01, 2015 5:44:20 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [“http-bio-8080”]
May 01, 2015 5:44:20 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [“ajp-bio-8009”]
May 01, 2015 5:44:20 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1220 ms
May 01, 2015 5:44:20 AM org.apache.catalina.core.StandardService
startInternal
INFO: Starting service Catalina
May 01, 2015 5:44:20 AM org.apache.catalina.core.StandardEngine
startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.61
May 01, 2015 5:44:21 AM org.apache.catalina.loader.WebappClassLoader
validateJarFile
INFO:
validateJarFile(/Users/ron/opt/t7i/l5/webapps/ROOT/WEB-INF/lib/javax.el-2.2.0.jar)

  • jar not loaded. See Servlet Spec 3.0, section 10.7.2. Offending class:
    javax/el/Expression.class
    May 01, 2015 5:44:23 AM org.apache.catalina.core.ContainerBase startInternal
    SEVERE: A child container failed during start
    java.util.concurrent.ExecutionException:
    org.apache.catalina.LifecycleException: Failed to start component
    [StandardEngine[Catalina].StandardHost[localhost].StandardContext]
    at java.util.concurrent.FutureTask.report(FutureTask.java:122)
    at java.util.concurrent.FutureTask.get(FutureTask.java:192)
    at
    org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1123)
    at
    org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:819)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at
    org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1575)
    at
    org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1565)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
    Caused by: org.apache.catalina.LifecycleException: Failed to start
    component
    [StandardEngine[Catalina].StandardHost[localhost].StandardContext]
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
    … 6 more
    Caused by: java.lang.SecurityException: no manifiest section for signature
    file entry javax/activation/DataContentHandlerFactory.class
    at
    sun.security.util.SignatureFileVerifier.verifySection(SignatureFileVerifier.java:440)
    at
    sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:295)
    at
    sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:238)
    at java.util.jar.JarVerifier.processEntry(JarVerifier.java:316)
    at java.util.jar.JarVerifier.update(JarVerifier.java:228)
    at java.util.jar.JarFile.initializeVerifier(JarFile.java:383)
    at java.util.jar.JarFile.getInputStream(JarFile.java:450)
    at
    org.apache.tomcat.util.scan.FileUrlJar.getEntryInputStream(FileUrlJar.java:97)
    at
    org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1964)
    at
    org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1931)
    at
    org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1916)
    at
    org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1330)
    at
    org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:889)
    at
    org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:386)
    at
    org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
    at
    org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
    at
    org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5416)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    … 6 more

May 01, 2015 5:44:23 AM org.apache.catalina.core.ContainerBase startInternal
SEVERE: A child container failed during start
java.util.concurrent.ExecutionException:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost]]
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1123)
at
org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:300)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.StandardService.startInternal(StandardService.java:443)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:739)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.startup.Catalina.start(Catalina.java:689)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:321)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:455)
Caused by: org.apache.catalina.LifecycleException: Failed to start
component [StandardEngine[Catalina].StandardHost[localhost]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1575)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1565)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.catalina.LifecycleException: A child container failed
during start
at
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1131)
at
org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:819)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
… 6 more

May 01, 2015 5:44:23 AM org.apache.catalina.startup.Catalina start
SEVERE: The required Server component failed to start so Tomcat is unable
to start.
org.apache.catalina.LifecycleException: Failed to start component
[StandardServer[8005]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at org.apache.catalina.startup.Catalina.start(Catalina.java:689)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:321)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:455)
Caused by: org.apache.catalina.LifecycleException: Failed to start
component [StandardService[Catalina]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at
org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:739)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
… 7 more
Caused by: org.apache.catalina.LifecycleException: Failed to start
component [StandardEngine[Catalina]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at
org.apache.catalina.core.StandardService.startInternal(StandardService.java:443)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
… 9 more
Caused by: org.apache.catalina.LifecycleException: A child container failed
during start
at
org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1131)
at
org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:300)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
… 11 more

May 01, 2015 5:44:23 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler [“http-bio-8080”]
May 01, 2015 5:44:23 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler [“ajp-bio-8009”]
May 01, 2015 5:44:23 AM org.apache.catalina.core.StandardService
stopInternal
INFO: Stopping service Catalina
May 01, 2015 5:44:23 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler [“http-bio-8080”]
May 01, 2015 5:44:23 AM org.apache.coyote.AbstractProtocol destroy
INFO: Destroying ProtocolHandler [“ajp-bio-8009”]On Thursday, April 30, 2015 at 1:52:57 AM UTC-6, Adam Cameron wrote:

G’day:
Whilst troubleshooting an issue that might exist in the Lucee express
install, I decided to try the WAR install instead. I will hasten to add my
knowledge / degree-of-comfort with Tomcat is minimal, but I can follow
instructions (if they’re available to find, that is).

I’ve done this:

  1. D/L the Windows 64-bit version of Tomcat 8 from their site
  2. unzip it into C:\apps\apache\tomcat\8. This is the first and only
    install of Tomcat on this computer
  3. create a setenv.bat file in the bin subdirectory of the above. This
    sets CATALINA_HOME to the directory above, and for good measure set
    JAVA_HOME to point to where my Java 8 JDK is installed.
  4. I add a user to the tomcat-users.xml file so I can access the app
    manager GUI.
  5. I start Tomcat with startup.bat. It starts A-OK. I can access the app
    manager GUI too. Everything is all-present and correct as far as my
    understanding of things goes.
  6. I stop Tomcat
  7. I D/L the latest (5.0.0.45) Lucee WAR file.
  8. I put it in Tomcat’s webapps subdir, and rename it as just lucee.war
  9. I start Tomcat. I see it deploying Lucee
  10. I return to the app manager UI, and see that Lucee is not running. I
    opt to start it.
  11. I get an error that it failed to start in the status area @ the top
    of the screen.
  12. consulting the catalina-out log, I see this lot:

30-Apr-2015 08:33:50.084 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Deploying web application
archive C:\apps\apache\tomcat\8\webapps\lucee.war
30-Apr-2015 08:33:50.410 SEVERE [localhost-startStop-1]
org.apache.catalina.core.ContainerBase.addChildInternal
ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/lucee]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:940)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1738)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.SecurityException: no manifiest section for
signature file entry
org/bouncycastle/jce/provider/JDKMessageDigest$RIPEMD256.class
at
sun.security.util.SignatureFileVerifier.verifySection(SignatureFileVerifier.java:440)
at
sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:295)
at
sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:238)
at java.util.jar.JarVerifier.processEntry(JarVerifier.java:316)
at java.util.jar.JarVerifier.update(JarVerifier.java:228)
at java.util.jar.JarFile.initializeVerifier(JarFile.java:383)
at java.util.jar.JarFile.getInputStream(JarFile.java:450)
at
org.apache.catalina.webresources.JarResource.getJarInputStreamWrapper(JarResource.java:46)
at
org.apache.catalina.webresources.AbstractArchiveResource.doGetInputStream(AbstractArchiveResource.java:218)
at
org.apache.catalina.webresources.AbstractResource.getInputStream(AbstractResource.java:94)
at
org.apache.catalina.util.ExtensionValidator.validateApplication(ExtensionValidator.java:152)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4992)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
… 10 more

30-Apr-2015 08:33:50.414 SEVERE [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Error deploying web
application archive C:\apps\apache\tomcat\8\webapps\lucee.war
java.lang.IllegalStateException: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/lucee]]
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:728)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:940)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1738)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

30-Apr-2015 08:33:50.419 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Deployment of web
application archive C:\apps\apache\tomcat\8\webapps\lucee.war has finished
in 334 ms

I have highlighted the bit I suspect is a problem.

I have experienced the following issue on two machines: one running
Windows 7 64-bit, and one running Windows 8.1 64-bit.

Questions:

  1. have I done something wrong? I could find no docs saying that to deploy
    Lucee as a WAR I have to do anything other than the default approach, and
    my understanding is “drop the WAR file into the webapps dir and start
    Tomcat” is all that’s required for that.
  2. Do I need to configure something for this library to work?
  3. Is there a problem with the WAR file?

I’m erring towards me doing something wrong, but not sure what to do about
working out what, other than asking here. I looked for other threads here
with ppl having similar issues, and also consulted the wiki, but found
nothing relevant.

Cheers.

–
Adam

3

Hi Adam,

Did you try executing the application context.

I actually did the same process yesterday when building our ContentBox war
and express
editions: http://integration.stg.ortussolutions.com/artifacts/ortussolutions/contentbox/2.1.0/

What I did, was the following:

  1. Download tomcat
  2. expand
  3. Drop lucee or contentbox war in webapps folder as “lucee” or “cb”
  4. Startup.sh or startup.bat
  5. Hit localhost:8080/luceeOn Thursday, April 30, 2015 at 2:52:57 AM UTC-5, Adam Cameron wrote:

G’day:
Whilst troubleshooting an issue that might exist in the Lucee express
install, I decided to try the WAR install instead. I will hasten to add my
knowledge / degree-of-comfort with Tomcat is minimal, but I can follow
instructions (if they’re available to find, that is).

I’ve done this:

  1. D/L the Windows 64-bit version of Tomcat 8 from their site
  2. unzip it into C:\apps\apache\tomcat\8. This is the first and only
    install of Tomcat on this computer
  3. create a setenv.bat file in the bin subdirectory of the above. This
    sets CATALINA_HOME to the directory above, and for good measure set
    JAVA_HOME to point to where my Java 8 JDK is installed.
  4. I add a user to the tomcat-users.xml file so I can access the app
    manager GUI.
  5. I start Tomcat with startup.bat. It starts A-OK. I can access the app
    manager GUI too. Everything is all-present and correct as far as my
    understanding of things goes.
  6. I stop Tomcat
  7. I D/L the latest (5.0.0.45) Lucee WAR file.
  8. I put it in Tomcat’s webapps subdir, and rename it as just lucee.war
  9. I start Tomcat. I see it deploying Lucee
  10. I return to the app manager UI, and see that Lucee is not running. I
    opt to start it.
  11. I get an error that it failed to start in the status area @ the top
    of the screen.
  12. consulting the catalina-out log, I see this lot:

30-Apr-2015 08:33:50.084 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Deploying web application
archive C:\apps\apache\tomcat\8\webapps\lucee.war
30-Apr-2015 08:33:50.410 SEVERE [localhost-startStop-1]
org.apache.catalina.core.ContainerBase.addChildInternal
ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/lucee]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:940)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1738)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.SecurityException: no manifiest section for
signature file entry
org/bouncycastle/jce/provider/JDKMessageDigest$RIPEMD256.class
at
sun.security.util.SignatureFileVerifier.verifySection(SignatureFileVerifier.java:440)
at
sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:295)
at
sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:238)
at java.util.jar.JarVerifier.processEntry(JarVerifier.java:316)
at java.util.jar.JarVerifier.update(JarVerifier.java:228)
at java.util.jar.JarFile.initializeVerifier(JarFile.java:383)
at java.util.jar.JarFile.getInputStream(JarFile.java:450)
at
org.apache.catalina.webresources.JarResource.getJarInputStreamWrapper(JarResource.java:46)
at
org.apache.catalina.webresources.AbstractArchiveResource.doGetInputStream(AbstractArchiveResource.java:218)
at
org.apache.catalina.webresources.AbstractResource.getInputStream(AbstractResource.java:94)
at
org.apache.catalina.util.ExtensionValidator.validateApplication(ExtensionValidator.java:152)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4992)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
… 10 more

30-Apr-2015 08:33:50.414 SEVERE [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Error deploying web
application archive C:\apps\apache\tomcat\8\webapps\lucee.war
java.lang.IllegalStateException: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/lucee]]
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:728)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:940)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1738)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

30-Apr-2015 08:33:50.419 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Deployment of web
application archive C:\apps\apache\tomcat\8\webapps\lucee.war has finished
in 334 ms

I have highlighted the bit I suspect is a problem.

I have experienced the following issue on two machines: one running
Windows 7 64-bit, and one running Windows 8.1 64-bit.

Questions:

  1. have I done something wrong? I could find no docs saying that to deploy
    Lucee as a WAR I have to do anything other than the default approach, and
    my understanding is “drop the WAR file into the webapps dir and start
    Tomcat” is all that’s required for that.
  2. Do I need to configure something for this library to work?
  3. Is there a problem with the WAR file?

I’m erring towards me doing something wrong, but not sure what to do about
working out what, other than asking here. I looked for other threads here
with ppl having similar issues, and also consulted the wiki, but found
nothing relevant.

Cheers.

–
Adam

4

Hi Adam,

Did you try executing the application context.

G’day Luis.

As per my original post, the process errors during deployment, so it’s
not running, so there’s nothing to browse to.

I’ve done some more testing: OpenBD, Lucee 4.5 both deploy and run fine. Am
currently D/Ling ContentBox and will try that, but unless I report back,
let’s assume that will work too.

At this point, I suspect something not right in the Lucee 5 WAR.

Can you pls confirm you JVM version (and if yer using a JDK or JRE) and
your Tomcat version. Also your OS might be relevant too? Dunno.

Anyone else had success?

CB is almost D/Led, so I’ll wait and try it before pressing SEND…yep it
installed fine.

So I have faith that Tomcat is working OK here.On Saturday, 2 May 2015 15:36:28 UTC+1, Luis Majano wrote:

–
Adam

5

I forgot to mention

Oh and I forgot to mention “cheers for trying to help me here”. I do
appreciate it, and it jogged my troubleshooting efforts into trying other
WAR files to check whether any others worked.

Thanks mate.On Saturday, 2 May 2015 15:40:33 UTC+1, Luis Majano wrote:

–
Adam

6

Adam

I just read your post again and realize a big difference. I was using 4,5. Not the 5 war. So maybe that’s why. I have not tried with 5 just yet. I am letting it brew some more.

However I will try it with 5 and see what I get.

Luis Majano
CEO
Ortus Solutions, Corp
www.ortussolutions.comP/F: 1-888-557-8057

Direct: (909) 248-3408

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

ContentBox Platform: http://www.gocontentbox.org

Linked In: http://www.linkedin.com/pub/3/731/483

Social: twitter.com/ortussolutions | twitter.com/coldbox | twitter.com/lmajano | twitter.com/gocontentboxOn Sat, May 2, 2015 at 11:15 AM, Adam Cameron <@Adam_Cameron> wrote:

On Saturday, 2 May 2015 15:36:28 UTC+1, Luis Majano wrote:

Hi Adam,

Did you try executing the application context.

G’day Luis.
As per my original post, the process errors during deployment, so it’s
not running, so there’s nothing to browse to.
I’ve done some more testing: OpenBD, Lucee 4.5 both deploy and run fine. Am
currently D/Ling ContentBox and will try that, but unless I report back,
let’s assume that will work too.
At this point, I suspect something not right in the Lucee 5 WAR.
Can you pls confirm you JVM version (and if yer using a JDK or JRE) and
your Tomcat version. Also your OS might be relevant too? Dunno.
Anyone else had success?
CB is almost D/Led, so I’ll wait and try it before pressing SEND…yep it
installed fine.
So I have faith that Tomcat is working OK here.

Adam

You received this message because you are subscribed to a topic in the Google Groups “Lucee” group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/lucee/ksnEL39gWQA/unsubscribe.
To unsubscribe from this group and all its topics, 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/b420dc24-9fe2-4d00-babf-84a4189eadac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

7

I forgot to mention there is a bug with the assets, where the java
application context is not accounted for. So the admin and resources do
not show up. I submitted a tiket for this.On Saturday, May 2, 2015 at 9:36:28 AM UTC-5, Luis Majano wrote:

Hi Adam,

Did you try executing the application context.

I actually did the same process yesterday when building our ContentBox war
and express editions:
http://integration.stg.ortussolutions.com/artifacts/ortussolutions/contentbox/2.1.0/

What I did, was the following:

  1. Download tomcat
  2. expand
  3. Drop lucee or contentbox war in webapps folder as “lucee” or “cb”
  4. Startup.sh or startup.bat
  5. Hit localhost:8080/lucee

On Thursday, April 30, 2015 at 2:52:57 AM UTC-5, Adam Cameron wrote:

G’day:
Whilst troubleshooting an issue that might exist in the Lucee express
install, I decided to try the WAR install instead. I will hasten to add my
knowledge / degree-of-comfort with Tomcat is minimal, but I can follow
instructions (if they’re available to find, that is).

I’ve done this:

  1. D/L the Windows 64-bit version of Tomcat 8 from their site
  2. unzip it into C:\apps\apache\tomcat\8. This is the first and only
    install of Tomcat on this computer
  3. create a setenv.bat file in the bin subdirectory of the above. This
    sets CATALINA_HOME to the directory above, and for good measure set
    JAVA_HOME to point to where my Java 8 JDK is installed.
  4. I add a user to the tomcat-users.xml file so I can access the app
    manager GUI.
  5. I start Tomcat with startup.bat. It starts A-OK. I can access the app
    manager GUI too. Everything is all-present and correct as far as my
    understanding of things goes.
  6. I stop Tomcat
  7. I D/L the latest (5.0.0.45) Lucee WAR file.
  8. I put it in Tomcat’s webapps subdir, and rename it as just lucee.war
  9. I start Tomcat. I see it deploying Lucee
  10. I return to the app manager UI, and see that Lucee is not running. I
    opt to start it.
  11. I get an error that it failed to start in the status area @ the top
    of the screen.
  12. consulting the catalina-out log, I see this lot:

30-Apr-2015 08:33:50.084 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Deploying web application
archive C:\apps\apache\tomcat\8\webapps\lucee.war
30-Apr-2015 08:33:50.410 SEVERE [localhost-startStop-1]
org.apache.catalina.core.ContainerBase.addChildInternal
ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/lucee]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:940)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1738)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.SecurityException: no manifiest section for
signature file entry
org/bouncycastle/jce/provider/JDKMessageDigest$RIPEMD256.class
at
sun.security.util.SignatureFileVerifier.verifySection(SignatureFileVerifier.java:440)
at
sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:295)
at
sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:238)
at java.util.jar.JarVerifier.processEntry(JarVerifier.java:316)
at java.util.jar.JarVerifier.update(JarVerifier.java:228)
at java.util.jar.JarFile.initializeVerifier(JarFile.java:383)
at java.util.jar.JarFile.getInputStream(JarFile.java:450)
at
org.apache.catalina.webresources.JarResource.getJarInputStreamWrapper(JarResource.java:46)
at
org.apache.catalina.webresources.AbstractArchiveResource.doGetInputStream(AbstractArchiveResource.java:218)
at
org.apache.catalina.webresources.AbstractResource.getInputStream(AbstractResource.java:94)
at
org.apache.catalina.util.ExtensionValidator.validateApplication(ExtensionValidator.java:152)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4992)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
… 10 more

30-Apr-2015 08:33:50.414 SEVERE [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Error deploying web
application archive C:\apps\apache\tomcat\8\webapps\lucee.war
java.lang.IllegalStateException: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/lucee]]
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:728)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:940)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1738)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

30-Apr-2015 08:33:50.419 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Deployment of web
application archive C:\apps\apache\tomcat\8\webapps\lucee.war has finished
in 334 ms

I have highlighted the bit I suspect is a problem.

I have experienced the following issue on two machines: one running
Windows 7 64-bit, and one running Windows 8.1 64-bit.

Questions:

  1. have I done something wrong? I could find no docs saying that to
    deploy Lucee as a WAR I have to do anything other than the default
    approach, and my understanding is “drop the WAR file into the webapps dir
    and start Tomcat” is all that’s required for that.
  2. Do I need to configure something for this library to work?
  3. Is there a problem with the WAR file?

I’m erring towards me doing something wrong, but not sure what to do
about working out what, other than asking here. I looked for other threads
here with ppl having similar issues, and also consulted the wiki, but found
nothing relevant.

Cheers.

–
Adam

8

Adam - I should reply you in a different way… :slight_smile:

Cheers for the clarification, Allen.

TBH I’m just testing, so not inclined to horse around too much getting it
to work. If what I did is supposed to work - you and others have clarified:
“yes”, then I’m OK to conclude the WAR is borked, and I’ll raise a ticket.

Perhaps I should have raised this on the “Lucee Supporters” forum where I’m
apparently guaranteed to get a response from actual Lucee (although Luis
comes close, I guess).

I’ll raise a Jira ticket, and move on.

[LDEV-335] - Lucee Sunday, 3 May 2015 13:34:02 UTC+1, Allen Weng wrote:

–
Adam

9

Adam - I should reply you in a different way… :slight_smile:

I can not just deploy the Lucee 5 WAR and have it work.

The same process when I deploy Railo 3/4, Lucee 4.5 war files on Tomcat 7

So my current solution is to follow the ‘upgrade’ steps, and make it work.

to reply your 3 questions, my 2 cents are

  1. I think your steps are OK, that’s what people usually will do.
  2. I hope we don’t need to configure anything, but now I do
  3. I personally think there’s problem with the custom WAR file.

I also noticed the jars in the bundles folder (from Lucee 5.0.45 jar (not
war) vs. the previous express edition I installed (I think it was
5.0.0.41?)) are different.

I can not list the details now but I can provide information after I turn
on that computer.)

AllenOn Sunday, May 3, 2015 at 2:32:33 AM UTC-4, Adam Cameron wrote:

On Sunday, 3 May 2015 04:37:15 UTC+1, Allen Weng wrote:

I had similar issue when I tried to deploy the Lucee 5 war to Tomcat 7/8

I found this article
lucee / Lucee / wiki / Lucee 5 Upgrading Railo — Bitbucket

and also compared with the file structure I installed from ‘Express’
edition, now it is working on my Tomcat

To be very clear, I’m not performing an upgrade, I’m performing a new
install. So “upgrade” guidance would not seem to apply in this situation.

–
Adam

10

I had similar issue when I tried to deploy the Lucee 5 war to Tomcat 7/8

I found this article
http://www.bytebucket.org/lucee/lucee/wiki/Lucee_5_Upgrading_Railo

and also compared with the file structure I installed from ‘Express’
edition, now it is working on my Tomcat

AllenOn Thursday, April 30, 2015 at 3:52:57 AM UTC-4, Adam Cameron wrote:

G’day:
Whilst troubleshooting an issue that might exist in the Lucee express
install, I decided to try the WAR install instead. I will hasten to add my
knowledge / degree-of-comfort with Tomcat is minimal, but I can follow
instructions (if they’re available to find, that is).

I’ve done this:

  1. D/L the Windows 64-bit version of Tomcat 8 from their site
  2. unzip it into C:\apps\apache\tomcat\8. This is the first and only
    install of Tomcat on this computer
  3. create a setenv.bat file in the bin subdirectory of the above. This
    sets CATALINA_HOME to the directory above, and for good measure set
    JAVA_HOME to point to where my Java 8 JDK is installed.
  4. I add a user to the tomcat-users.xml file so I can access the app
    manager GUI.
  5. I start Tomcat with startup.bat. It starts A-OK. I can access the app
    manager GUI too. Everything is all-present and correct as far as my
    understanding of things goes.
  6. I stop Tomcat
  7. I D/L the latest (5.0.0.45) Lucee WAR file.
  8. I put it in Tomcat’s webapps subdir, and rename it as just lucee.war
  9. I start Tomcat. I see it deploying Lucee
  10. I return to the app manager UI, and see that Lucee is not running. I
    opt to start it.
  11. I get an error that it failed to start in the status area @ the top
    of the screen.
  12. consulting the catalina-out log, I see this lot:

30-Apr-2015 08:33:50.084 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Deploying web application
archive C:\apps\apache\tomcat\8\webapps\lucee.war
30-Apr-2015 08:33:50.410 SEVERE [localhost-startStop-1]
org.apache.catalina.core.ContainerBase.addChildInternal
ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/lucee]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:940)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1738)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.SecurityException: no manifiest section for
signature file entry
org/bouncycastle/jce/provider/JDKMessageDigest$RIPEMD256.class
at
sun.security.util.SignatureFileVerifier.verifySection(SignatureFileVerifier.java:440)
at
sun.security.util.SignatureFileVerifier.processImpl(SignatureFileVerifier.java:295)
at
sun.security.util.SignatureFileVerifier.process(SignatureFileVerifier.java:238)
at java.util.jar.JarVerifier.processEntry(JarVerifier.java:316)
at java.util.jar.JarVerifier.update(JarVerifier.java:228)
at java.util.jar.JarFile.initializeVerifier(JarFile.java:383)
at java.util.jar.JarFile.getInputStream(JarFile.java:450)
at
org.apache.catalina.webresources.JarResource.getJarInputStreamWrapper(JarResource.java:46)
at
org.apache.catalina.webresources.AbstractArchiveResource.doGetInputStream(AbstractArchiveResource.java:218)
at
org.apache.catalina.webresources.AbstractResource.getInputStream(AbstractResource.java:94)
at
org.apache.catalina.util.ExtensionValidator.validateApplication(ExtensionValidator.java:152)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4992)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
… 10 more

30-Apr-2015 08:33:50.414 SEVERE [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Error deploying web
application archive C:\apps\apache\tomcat\8\webapps\lucee.war
java.lang.IllegalStateException: ContainerBase.addChild: start:
org.apache.catalina.LifecycleException: Failed to start component
[StandardEngine[Catalina].StandardHost[localhost].StandardContext[/lucee]]
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:728)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:940)
at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1738)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

30-Apr-2015 08:33:50.419 INFO [localhost-startStop-1]
org.apache.catalina.startup.HostConfig.deployWAR Deployment of web
application archive C:\apps\apache\tomcat\8\webapps\lucee.war has finished
in 334 ms

I have highlighted the bit I suspect is a problem.

I have experienced the following issue on two machines: one running
Windows 7 64-bit, and one running Windows 8.1 64-bit.

Questions:

  1. have I done something wrong? I could find no docs saying that to deploy
    Lucee as a WAR I have to do anything other than the default approach, and
    my understanding is “drop the WAR file into the webapps dir and start
    Tomcat” is all that’s required for that.
  2. Do I need to configure something for this library to work?
  3. Is there a problem with the WAR file?

I’m erring towards me doing something wrong, but not sure what to do about
working out what, other than asking here. I looked for other threads here
with ppl having similar issues, and also consulted the wiki, but found
nothing relevant.

Cheers.

–
Adam

11

I had similar issue when I tried to deploy the Lucee 5 war to Tomcat 7/8

I found this article
lucee / Lucee / wiki / Lucee 5 Upgrading Railo — Bitbucket

and also compared with the file structure I installed from ‘Express’
edition, now it is working on my Tomcat

To be very clear, I’m not performing an upgrade, I’m performing a new
install. So “upgrade” guidance would not seem to apply in this situation.On Sunday, 3 May 2015 04:37:15 UTC+1, Allen Weng wrote:

–
Adam

12

Just out of curiosity. Try removing all other web apps except for the lucee 5 war, then try startin. Tomcat up.

That’s the same error I get when trying to configure Lucee 5 server wide. I reported my particular experience as a blocker on the issue tracker.

13

In my attempts to deploy the Lucee 5 war where the deployment fails, it is
in fact the only thing deployed on that instance of Tomcat on both Tomcat 7
and Tomcat 8.On Monday, May 4, 2015 at 9:20:16 PM UTC-6, Jesse Shaffer wrote:

Just out of curiosity. Try removing all other web apps except for the
lucee 5 war, then try startin. Tomcat up.

That’s the same error I get when trying to configure Lucee 5 server wide.
I reported my particular experience as a blocker on the issue tracker.

14

I encountered the same problem. Actually, a few, related issues. My setup:
OS X 10.3, Oracle Java 1.8.0u45, Tomcat 8.0.23, and Lucee 5.0.0.49.

Bouncy Castle
An exception on starting Tomcat right away:
java.lang.SecurityException: no manifiest section for signature file entry
org/bouncycastle/asn1/ocsp/ResponderID.class

I went into WEB-INF/lib and found bcprov-jdk14-1-36-0.jar, which apparently
is intended for JDK 1.4. I replaced the old version with a newer one
(bcprov-jdk15on-152.jar)
from https://www.bouncycastle.org/latest_releases.html. That resolved that
problem. On to the next.

Java Activation
This was a little tricky to resolve because I was getting this error in the
Tomcat output:
java.lang.SecurityException: Invalid signature file digest for Manifest
main attributes

That didn’t point me to the right JAR to deal with. From WEB-INF/lib, I
executed the following:
for F in *.jar; do echo $F; jarsigner -verify $F; done

The culprit was sun-activation-1-1-0.jar. So, I grabbed an updated version
of that from JavaBeans Activation Framework 1.1 Download. I
removed the old version and put the new one in as sun-activation-1-1-1.jar.

PDFRenderer
While running the JAR signature verification above, I also the same sort of
“java.lang.SecurityException: Invalid signature file digest for Manifest
main attributes” error on PDFRenderer-1-0-5.jar. Since I won’t be doing any
PDF generation, I just deleted that file.

Those three JAR adjustments let Lucee start up and function properly, as
far as I can tell.

I did notice that shortly after the first start, Lucee downloaded all of
it’s JARs to $TOMCAT_HOME/lucee-server/bundles/:
download:flex.messaging.opt:3.3.0.22497
download:openamf:1.5.8
download:sun.jndi.ldapsec:1.2.4
download:xml.apis:1.3.2
…
download:PDFRenderer:1.0.5
…
download:bcprov.jdk14:1.36.0
…
download:sun.activation:1.1.0
…

That’s a little concerning, since I’ve already established that three of
them are no good.

-joseph

15

Using the JARs (not WARs) from the web site:

https://bitbucket.org/lucee/lucee/downloads/lucee-5.0.0.49-jars.zip

All of this still happens. I followed Joseph’s instructions and Tomcat now
runs.

16

Left out - one other required step was to find and download lucee-inst.jar
from Bitbucket, because the JAR .zip on the web site doesn’t contain it but
these instructions still refer to it:

https://bitbucket.org/lucee/lucee/wiki/Installing%20and%20configuring%20Lucee%20(JAR%20files)%20on%20Windows

17

For anyone following this thread, I was able to successfully deploy and
start the current snapshot WAR (5.0.0.84-SNAPSHOT.war) this morning on both
Tomcat 7 and Tomcat 8 (current release versions, respectively) running on
Java 1.8.0_60 on Mac OS X 10.10.5. I didn’t do any testing other than
verifying that it would deploy successfully and then start. I was able to
access the Lucee 5 server and web admins.

Seems promising.

Thanks, Micha, for following up on this in the bug-tracker.On Monday, June 1, 2015 at 5:11:22 PM UTC-6, Joseph Lamoree wrote:

I encountered the same problem. Actually, a few, related issues. My setup:
OS X 10.3, Oracle Java 1.8.0u45, Tomcat 8.0.23, and Lucee 5.0.0.49.

Bouncy Castle
An exception on starting Tomcat right away:
java.lang.SecurityException: no manifiest section for signature file entry
org/bouncycastle/asn1/ocsp/ResponderID.class

I went into WEB-INF/lib and found bcprov-jdk14-1-36-0.jar, which
apparently is intended for JDK 1.4. I replaced the old version with a newer
one (bcprov-jdk15on-152.jar) from
bouncycastle.org. That resolved that
problem. On to the next.

Java Activation
This was a little tricky to resolve because I was getting this error in
the Tomcat output:
java.lang.SecurityException: Invalid signature file digest for Manifest
main attributes

That didn’t point me to the right JAR to deal with. From WEB-INF/lib, I
executed the following:
for F in *.jar; do echo $F; jarsigner -verify $F; done

The culprit was sun-activation-1-1-0.jar. So, I grabbed an updated version
of that from JavaBeans Activation Framework 1.1 Download. I
removed the old version and put the new one in as sun-activation-1-1-1.jar.

PDFRenderer
While running the JAR signature verification above, I also the same sort
of “java.lang.SecurityException: Invalid signature file digest for Manifest
main attributes” error on PDFRenderer-1-0-5.jar. Since I won’t be doing any
PDF generation, I just deleted that file.

Those three JAR adjustments let Lucee start up and function properly, as
far as I can tell.

I did notice that shortly after the first start, Lucee downloaded all of
it’s JARs to $TOMCAT_HOME/lucee-server/bundles/:
download:flex.messaging.opt:3.3.0.22497
download:openamf:1.5.8
download:sun.jndi.ldapsec:1.2.4
download:xml.apis:1.3.2
…
download:PDFRenderer:1.0.5
…
download:bcprov.jdk14:1.36.0
…
download:sun.activation:1.1.0
…

That’s a little concerning, since I’ve already established that three of
them are no good.

-joseph