I realized this after a week running Lucee an my development server: If i
visit the Tomcat Administration, i get an exception from Lucee.
On this server, i moved from Railo to Lucee.
Any idea, why this happens?
Thanks!
Lucee 4.5.1.000 Error (missinginclude)> Message Page /index.cfm [D:\Tomcat\WebApps\manager\index.cfm] not found
Java Stacktrace Page /index.cfm [D:\Tomcat\WebApps\manager\index.cfm]
not found
at lucee.runtime.PageSourceImpl.loadPage(Unknown Source):-1
at lucee.runtime.PageContextImpl.doInclude(Unknown Source):-1
at lucee.runtime.listener.ClassicAppListener._onRequest(Unknown
Source):-1
at lucee.runtime.listener.MixedAppListener.onRequest(Unknown
Source):-1
at lucee.runtime.PageContextImpl.execute(Unknown Source):-1
at lucee.runtime.PageContextImpl.execute(Unknown Source):-1
at lucee.runtime.engine.CFMLEngineImpl.serviceCFML(Unknown Source):-1
at lucee.loader.servlet.CFMLServlet.service(Unknown Source):-1
at javax.servlet.http.HttpServlet.service(HttpServlet.java:725):725
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291):291
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206):206
at
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52):52
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239):239
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206):206
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219):219
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106):106
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501):501
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142):142
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79):79
at mod_cfml.core.invoke(core.java:131):131
at
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:610):610
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88):88
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:516):516
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1086):1086
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:659):659
at
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:223):223
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1558):1558
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1515):1515
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142):1142
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617):617
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61):61
at java.lang.Thread.run(Thread.java:745):745
order has to be important. otherwise how would Tomcat know which file
to use when more than one option meets the criteria…?On 2/9/2015 9:27 AM, Martin Schaible wrote:
I also understand that the order is important but why can’t index.cfm be at
the top of the list, as this is the most used one for us.On Tuesday, February 10, 2015 at 3:13:12 AM UTC+1, Igal wrote:
order has to be important. otherwise how would Tomcat know which file to
use when more than one option meets the criteria…?
I also understand that the order is important but why can’t index.cfm
be at the top of the list, as this is the most used one for us.
On Tuesday, February 10, 2015 at 3:13:12 AM UTC+1, Igal wrote:
order has to be important. otherwise how would Tomcat know which
file to use when more than one option meets the criteria...?
On 2/9/2015 9:27 AM, Martin Schaible wrote:
that is odd:
Wrong:
<welcome-file-list>
* <welcome-file>index.cfm</welcome-file>*
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
Right:
<welcome-file-list>
<welcome-file>index.html</welcome-file>
<welcome-file>index.htm</welcome-file>
<welcome-file>index.jsp</welcome-file>
*<welcome-file>index.cfm</welcome-file>*
</welcome-file-list>
I didn't knew, that the order is important.
--
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/3f957343-f547-453f-b225-f60cee6c46b0%40googlegroups.com
<https://groups.google.com/d/msgid/lucee/3f957343-f547-453f-b225-f60cee6c46b0%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout
<https://groups.google.com/d/optout>.
order has to be important. otherwise how would Tomcat know which file to
use when more than one option meets the criteria…?
I agree with this, same as in IIS. I can not understand, how Tomcat deals
with this list. If index.cfm is #1 in the list, and the file is not there,
Tomcat should try the next item in the list until he finds index.jsp. Big
difference to IIS, which behaves like this.