Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Troubleshooting: "[Servlet Error]-[Failed to load listener: WebAppLifeCycleListenerBoot]” at startup (WebSphere 6.1)

Updated on October 2, 2015

Symptom

You are installing Process Commander Version 5.5 on WebSphere Application Server Version 6.1 running on the RedHat Enterprise LINUX v5.2 operating system. When deploying the Process Commander core application component EAR file (prpc_ws61.ear) and the WAR files for the Database Utilities application (prdbutil.war) and the System Management application (prsysmgmt.war), you encounter the following error message:

[Servlet Error]-[Failed to load listener: com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot]: java.lang.ClassNotFoundException: com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot

Follow the suggested approach to restore the overwritten manifest.mf file that causes this problem.

Explanation

When the Process Command EAR was repackaged, the manifest.mf file located in the directory path <application_server_host>webapps\prweb\META-INF was overwritten, causing the manifest.mf file to become incomplete:

Manifest-Version: 1.0

Created-By: 1.4.2_14 (Sun Microsystems Inc.)

Here is an example of a complete manifest.mf file:

Manifest-Version: 1.0

Ant-Version: Apache Ant 1.6.5

Created-By: 1.5.0_12-b04 (Sun Microsystems Inc.)

Build-For: v55_relcand_0068

Build-Date: 2009-05-22 16.25 EDT

Build-Target: J2EE 1.4 Pega-Assembly-Date: 2009-05-22 16.25 EDT

Class-Path: APP-INF/lib/prbootstrap.jar APP-INF/lib/jsr94-1.0.jar APP- INF/lib/prdbcp.jar APP-INF/lib/prderby-10.1.1.0.jar APP-INF/lib/prder byclient-10.1.1.0.jar

 

Solution

To recover the file webapps\prweb\META-INF\manifest.mf, complete the following steps:

  1. Replace the manifest.mf file in the EAR that is failing with the manifest.mf from the EAR file provided by Process Commander, prpc_ws61.ear.
  2. Use the command jar -cvfM to re-archive the EAR file to ensure that the manifest.mf file does not lose its contents.

 

Related Topics

PDF documentPegaRULES Process Commander Release V5.5 SP1, Installing on WebSphere 6.1 Application Servers

Java Reference

wwwjar-The Java Archive Tool

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us