Troubleshooting
Problem
When the BPF web application is started in Weblogic Server 10.0.2 or later, a number of harmless "Failed to load servlet Class" exceptions are recorded in the stderr log file. Although these exceptions are harmless, they can be confusing to the user.
Symptom
The following exceptions are logged in the stderr log file whenever the BPF web application is started in Weblogic Server 10.0.2 or later:
Failed to load servlet Class: download1Ignoring: unable to load class:java.lang.ClassNotFoundException: download1 at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)Failed to load servlet Class: download1Ignoring: unable to load class:java.lang.ClassNotFoundException: download1 at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)Failed to load servlet Class: com.filenet.wcm.appint.server.WcmUploadIgnoring: unable to load class:java.lang.ClassNotFoundException: com.filenet.wcm.appint.server.WcmUpload at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)Failed to load servlet Class: com.filenet.wcm.toolkit.server.servlet.WcmContentDownloadServletIgnoring: unable to load class:java.lang.ClassNotFoundException: com.filenet.wcm.toolkit.server.servlet.WcmContentDownloadServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)Failed to load servlet Class: com.filenet.wcm.toolkit.server.servlet.WcmContentUploadServletIgnoring: unable to load class:java.lang.ClassNotFoundException: com.filenet.wcm.toolkit.server.servlet.WcmContentUploadServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)Failed to load servlet Class: com.filenet.wcm.appint.server.WcmUploadIgnoring: unable to load class:java.lang.ClassNotFoundException: com.filenet.wcm.appint.server.WcmUpload at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)Failed to load servlet Class: com.filenet.wcm.toolkit.server.servlet.WcmContentDownloadServletIgnoring: unable to load class:java.lang.ClassNotFoundException: com.filenet.wcm.toolkit.server.servlet.WcmContentDownloadServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)Failed to load servlet Class: com.filenet.wcm.toolkit.server.servlet.WcmContentUploadServletIgnoring: unable to load class:java.lang.ClassNotFoundException: com.filenet.wcm.toolkit.server.servlet.WcmContentUploadServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)<Apr 20, 2010 11:32:19 AM MST> <Warning> <Connector> <BEA-190155> <Compliance checking/v
Cause
Three servlets are declared in the BPF web.xml file. However, these servlets are not used by BPF and the underlying class files for them are not included in BPF web application.
Resolving The Problem
To remove the unnecessary servlet declarations from the BPF web.xml file, perform the following steps:
1) Stop the BPF web application.
2) Go to the BPF deployment folder.
3) Remove the following elements from the /WEB-INF/web.xml file:
<servlet id="Servlet_3">
<servlet-name>upload</servlet-name>
<description>This servlet is used to relay content upload requests and responses between the administrative applets running on the client machine and the content engine.</description>
<servlet-class>com.filenet.wcm.appint.server.WcmUpload</servlet-class>
</servlet>
<servlet id="Servlet_6">
<servlet-name>downloadProxy</servlet-name>
<description>This servlet is used to relays content download requests and responses between the administrative applets running on the client machine and the content engine.</description>
<servlet-class>com.filenet.wcm.toolkit.server.servlet.WcmContentDownloadServlet</servlet-class>
</servlet>
<servlet id="Servlet_7">
<servlet-name>uploadProxy</servlet-name>
<description>This servlet is used to relays content upload requests and responses between the administrative applets running on the client machine and the content engine.</description>
<servlet-class>com.filenet.wcm.toolkit.server.servlet.WcmContentUploadServlet</servlet-class>
</servlet>
<servlet-mapping id="ServletMapping_3">
<servlet-name>upload</servlet-name>
<url-pattern>/upload/*</url-pattern>
</servlet-mapping>
<servlet-mapping id="ServletMapping_6">
<servlet-name>downloadProxy</servlet-name>
<url-pattern>/downloadProxy</url-pattern>
</servlet-mapping>
<servlet-mapping id="ServletMapping_7">
<servlet-name>uploadProxy</servlet-name>
<url-pattern>/uploadProxy</url-pattern>
</servlet-mapping>
4) Redeploy the BPF web application.
The "Failed to load servlet Class" exceptions are no longer generated.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21456873