Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Lucee 5/Tomcat fails to deploy more than one host

Description

this post on dev.lucee is what I see

https://dev.lucee.org/t/lucee-5-0-0-235-on-tomcat-8-0-33-does-not-auto-deploy-to-additional-host/1530

still have the same problem on

Lucee 5.2.x
Tomcat 8.5
Apache 2.4
Java 8
mod_jk/mod_cfml

also see this error
org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfiguration

try the work-around on https://luceeserver.atlassian.net/browse/LDEV-257 and it is not working

Thank you!

Environment

None

Activity

Show:

Christoph Kindle 1 February 2018 at 00:07

I placed the 3rd party jars in the domain’s WEB-INF/lucee/lib folder and they were found. I'm quite sure that with the first Lucee 5 version this didn't work. That's why I placed the jars in the /opt/lucee/lib folder.
So it's solved for me.
Thank you very much Allen for your help.

Christoph Kindle 31 January 2018 at 22:27
Edited

I updated to Lucee 5.2.6.53-SNAPSHOT
Then I deleted the WEB-INF Folder of a domain in /vhosts/[domain]/WEB-INF
Then I deleted all 3rd party jars in /opt/lucee/lib, so that there is only the file lucee-5.2.1.9.jar
Restart of Lucee ... and it worked.

Unfortunately for my report tool. I have to try, if I can make it work with the new Lucee version.

Allen Weng 30 January 2018 at 18:04

Well... if you do the followings:

1. stop lucee
2. kill all those bad folders/files
3. temporarily remove these 2 jars from /opt/lucee/lib folder
4. start lucee

will your multi-hosts environment work in Lucee 5.2.5?

Christoph Kindle 30 January 2018 at 13:10
Edited

In catalina.properties nothing was changed by myself.

With Lucee 4.5 I had the 3rd party jars for JasperReports in the domains lib folders. With Lucee 5 this wasn't any more working, or at least not with the JasperReports jars.
Therefore I had to put them in the /opt/lucee/lib folder.
With Lucee 4.5 I hadn't to put the mysql jar on the webserver. With Lucee 5 I had to put it on the server, so that the reports could connect to the database.

Allen Weng 30 January 2018 at 12:43

Mmm.. I am not talking about the jars in /opt/lucee/lib, that's shipped by Lucee, and usually you don't put 3rd party jars there.... I mean the the jars included in classpath defined in /opt/lucee/tomcat/conf/catalina.properties

also I don't think you need to put mysql 5.1.41 jar there, Lucee will only use the mysql jdbc jar loaded via OSGi bundle.

In the beginning I had the same issue since Lucee 5.2.2.71, so it is not something new.

Details

Assignee

Reporter

Priority

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Created 8 November 2017 at 20:31
Updated 9 September 2019 at 14:20

Flag notifications