WebSphere Process Server messages     Operating Systems: All supported

EJPPC

EJPPC0001E: An AdminException was caught during portlet.xml validation. The Message was: {0}
Problem The validation of the portlet.xml within this archive has failed. Please check the ffdc log files for more information.
User response Please correct the reported problem and analyze the log files for the cause of the exception.
EJPPC0002E: A FileNotFoundException was caught. The Message was: {0}
Problem There was an error installing the application due to a missing file. Please check the ffdc log files for more information.
User response Please correct the reported problem and analyze the log files for the cause of the exception.
EJPPC0003E: An IOException was caught. The Message was: {0}
Problem There was an exception when accessing a file on the system. Please check the ffdc log files for more information.
User response Please correct the reported problem and analyze the log files for the cause of the exception.
EJPPC0004E: portlet.xml validation caught a ParserConfigurationException. The Message was: {0}
Problem portlet.xml validation caught a ParserConfigurationException. Please check the ffdc log files for more information.
User response Please correct the reported problem and analyze the log files for the cause of the exception.
EJPPC0005E: portlet.xml validation caught a SAXException. The Message was: {0}
Problem The portlet.xml contained within this archive does not seem to match the schema and needs to be correct.
User response Please correct the reported problem and analyze the log files for the cause of the exception.
EJPPC0006E: Portlet and Servlet names must be different within portlet.xml and web.xml.
Problem In order to address portlets via a URL, portlet and servlet names must be different within a WAR file.
User response Please correct the reported problem and redeploy the application.
EJPPC0007E: An error was detected: a servletmapping cannot be the same as /<portletname>/* or /portlet/<portletname>/*.
Problem A servletmapping cannot be the same as /<portletname>/* or /portlet/<portletname>/*.
User response Please correct the reported problem and redeploy the application.
EJPPC0008E: A fatal error occurred when parsing portlet.xml : {0}
Problem A fatal error occurred when parsing portlet.xml.
User response Please check the log files for the cause of this exception.
EJPPC0009E: An error occurred when parsing portlet.xml : {0}
Problem An error occurred when parsing portlet.xml.
User response Please check the log files for the cause of this exception.
EJPPC0010W: The parser indicates a warning when parsing portlet.xml : {0}
Problem There was a warning.
User response Please check your portlet.xml and try to fix the problem.
EJPPC0011I: Validation of portlet.xml completed.
Problem The portlet.xml contained within this archive has passed validation successfully.
User response No action required.
EJPPC0101W: Error occurred when loading the portlet deployment descriptor extension file. Default configurations are used.
Problem An Exception was received when trying to load the file portlet deployment descriptor extension file.
User response Please analyze the log files for the cause of the error.
EJPPC0102W: Error occurred when reading the configuration data of the web application.
Problem An Exception was received while reading the configuration data of the web application. The portlet container will not be available for this application.
User response Please analyze the log files for the cause of the error.
EJPPC0201E: Error occurred during MBean activation for MBeans of type portlet and portletapplication
Problem An AdminException was received when trying to activate the MBean.
User response Please analyze the log files for the cause of the error.
EJPPC0202E: Error occurred during MBean deactivation for MBeans of type portlet and portletapplication
Problem An AdminException was received when trying to deactivate the MBean.
User response Please analyze the log files for the cause of the error.
EJPPC0203E: Error occurred when sending starting notification for a portletapplication
Problem An MBeanException was received when trying to send a Notification.
User response Please analyze the log files for the cause of the error.
EJPPC0204E: Error occurred during Listener registration within the portletapplication MBean
Problem A MalformedObjectNameException was received when trying to register a Listener to the MBean.
User response Please validate the name of the MBean is specified correctly and analyze the log files for the cause of the error.
EJPPC0205E: Error occurred during unregistration Listener within the portletapplication MBean
Problem An Exception was received when trying to unregister a Listener from the MBean.
User response Please verify that there was a Listener registered to the MBean and that the MBean instance exists. You can analyze the log files for the cause of the error.
EJPPC0206E: Error occurred during notification handling within the portletapplication MBean
Problem An exception was received when the MBean notification handler received a message.
User response Please analyze the log files for the cause of the error.
EJPPC0220E: There was an exception when trying to create a StatsGroup or StatsInstance for portlet application : {0}
Problem For the initialisation of PMI measurements for a portlet application a StatsGroup and StatsInstance needs to be registered that identifies this portlet application within the system.
User response Please check that the portlet application is installed and see the log files for the original cause of the excetpion.
EJPPC0221E: There was an exception when trying to remove a StatsInstance for portlet application : {0}
Problem When an application is stopped it is removed from the PMI tree.
User response Please check that the portlet application is installed and see the log files for the original cause of the excetpion.
EJPPC0222E: There was an exception when trying to create a StatsGroup or StatsInstance for portlet : {0}
Problem For the initialisation of PMI measurements for a portlet a StatsGroup and StatsInstance needs to be regiustered that identifies this portlet application within the system.
User response Please check that the portlet is installed and see the log files for the original cause of the excetpion.
EJPPC0230E: There was an exception when trying to create the collaborators.
Problem Not all capabilities of the portlet container will be available since not all collaborators have been initialized.
User response Please check that the plugin.xml has the correct format and the referenced class exists.
EJPPC0240E: Error occurred during container service access. Expected ExtInformationProviderWrapper not found, but was: {0}.
Problem The portlet container expects the ExtInformationProviderWrapper to be the latest container service wrapper. No custom PortletContainerInvokerCollaborator must wrap this container service later.
User response Please check that there is no PortletContainerInvokerCollaborator configured to be latest.
EJPPC0241E: There was an exception when trying to add a dynamic content provider. A portlet url could not be created.
Problem The dynamic content provider allows to dynamically add the correct portlet url to the cached content.
User response Please analyze the log files for the cause of the error.
EJPPC0242E: Error occurred during lookup in application extension registry.
Problem Collaborators used in applications will not work.
User response Please check the jndi settings for the application extension registry.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.portletcontainer.runtime.resources.Messages.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)