DMP Consumer 6.0 m010 ApplicationContextFacade error:

Forum|Forum|14 years ago
February 9, 2012
4 replies
819 views

When I perform a search (simple or advanced) the search results are:

The page you requested contains an error and cannot be displayed.

Error Status: 500

Unable to find a value for "contextPath" in object of class
"org.apache.catalina.core.
ApplicationContextFacade" using operator "."

Has anyone seen and fix this yet? Oh. Hmmm. Just realized: Tomcat 5.0.18.
Wonder if that's too old for DMP/C 6.0?

--
Paul Nagai

C

ClayHelberg

18-Opal

Hi Paul--

I haven't tested it, but from the specs, it looks like your hypothesis
is probably on target.

The DMP Dev Guide for 6.0 says: "the WAR file can be deployed in any
servlet container, application server, or web server supporting the JSP
2.0 and Servlet 2.4 standards". According to

N

naglists

Author

1-Visitor

Am now fighting with different DMP Consumer errors using the DMP
default/demo project (so not one of my moderately customized for 5.4 mXXXX
"upgraded/migrated" to 6.0). Sigh. This with a new or near new Tomcat/Java
environment. For what it's worth, the standalone DMP Consumer module does
load and search OK so this confirms Clay's confirm of my assume.

(My customized projects do not load, however, so clearly I've got some mods
to un-mod or re-mod for the 6.0 environment.)

Anyhow, I get three different results when attempting to load the web
application via Tomcat. On the first attempt:

javax.servlet.ServletException: Error instantiating servlet class
com.arbortext.dmc.consumer.index_jspx

org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)

org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)

org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
java.lang.Thread.run(Unknown Source)

root cause

java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
org.apache.jasper.runtime.HttpJspBase.<clinit>(HttpJspBase.java:43)
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
Source)
java.lang.reflect.Constructor.newInstance(Unknown Source)
java.lang.Class.newInstance0(Unknown Source)
java.lang.Class.newInstance(Unknown Source)

org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)

org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)

org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
java.lang.Thread.run(Unknown Source)

root cause

java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory

org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1680)

org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526)
org.apache.jasper.runtime.HttpJspBase.<clinit>(HttpJspBase.java:43)
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
Source)
java.lang.reflect.Constructor.newInstance(Unknown Source)
java.lang.Class.newInstance0(Unknown Source)
java.lang.Class.newInstance(Unknown Source)

org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)

org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)

org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
java.lang.Thread.run(Unknown Source)

note The full stack trace of the root cause is available in the Apache
Tomcat/6.0.35 logs.

C

ClayHelberg

18-Opal

Hi Paul--

Check that the Apache Commons Logging library is available to Tomcat.
See this page:

N

naglists

Author

1-Visitor

Clay, FTW!

Duh.