lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aliaksandr Zhuhrou (Created) (JIRA)" <>
Subject [jira] [Created] (SOLR-3244) New Admin UI doesn't work on tomcat
Date Wed, 14 Mar 2012 09:39:37 GMT
New Admin UI doesn't work on tomcat

                 Key: SOLR-3244
             Project: Solr
          Issue Type: Bug
          Components: web gui
    Affects Versions: 4.0
            Reporter: Aliaksandr Zhuhrou

I am currently unable to open admin interface when using war deployment under tomcat server.
The stack trace:

SEVERE: Servlet.service() for servlet [LoadAdminUI] in context with path [/solr] threw exception
	at org.apache.solr.servlet.LoadAdminUiServlet.doGet(
	at javax.servlet.http.HttpServlet.service(
	at javax.servlet.http.HttpServlet.service(
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(
	at org.apache.solr.servlet.SolrDispatchFilter.doFilter(
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(
	at org.apache.catalina.core.StandardWrapperValve.invoke(
	at org.apache.catalina.core.StandardContextValve.invoke(
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(
	at org.apache.catalina.core.StandardHostValve.invoke(
	at org.apache.catalina.valves.ErrorReportValve.invoke(
	at org.apache.catalina.valves.AccessLogValve.invoke(
	at org.apache.catalina.core.StandardEngineValve.invoke(
	at org.apache.catalina.connector.CoyoteAdapter.service(
	at org.apache.coyote.http11.AbstractHttp11Processor.process(
	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(
	at java.util.concurrent.ThreadPoolExecutor.runWorker(
	at java.util.concurrent.ThreadPoolExecutor$

Tomcat version: Apache Tomcat/7.0.23
Java version: jdk1.7.0_02

I did some debugging and found that the problem related that 
it delegates the resolving of resource path to the org.apache.naming.resources.WARDirContext
which simply returns null for any input parameters:

  * Return the real path for a given virtual path, if possible; otherwise
  * return <code>null</code>.
  * @param path The path to the desired resource
protected String doGetRealPath(String path) {
  return null;

Need to check specification, because it may be actually the tomcat bug.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message