Express (Distributed operating systems), v8.0 > Reference > Messages
EJPPC
EJPPC0001E: An AdminException exception was created during the portlet.xml file validation. Error: {0}
Explanation The validation of the portlet.xml file within this archive has failed. Action Correct the reported problem and analyze the ffdc log files to determine the cause of the exception.
EJPPC0002E: A FileNotFoundException was created. Error: {0}
Explanation There was an error installing the application due to a missing file. Action Correct the reported problem and analyze the ffdc log files for the cause of the exception.
EJPPC0003E: An IOException was created. Error: {0}
Explanation There was an exception when accessing a file on the system. Action Correct the reported problem and analyze the ffdc log files for the cause of the exception.
EJPPC0004E: portlet.xml validation caught a ParserConfigurationException. Error: {0}
Explanation The portlet.xml validation caught a ParserConfigurationException. Action Correct the reported problem and analyze the ffdc log files for the cause of the exception.
EJPPC0005E: portlet.xml validation caught a SAXException. Error: {0}
Explanation The portlet.xml contained within this archive does not match the schema and needs to be corrected. Action Correct the reported problem and analyze the System log files for the cause of the exception.
EJPPC0006E: Portlet and servlet names must be different within the portlet.xml and web.xml files.
Explanation To address portlets through a URL, portlet and servlet names must be unique within a WAR file. Action Specify unique names for the portlet and servlet within the portlet.xml and web.xml files and redeploy the application.
EJPPC0007E: The servlet mapping is the same as / <portletname>/* or /portlet/ <portletname>/*.
Explanation A servlet mapping cannot be the same as / <portletname>/* or /portlet/ <portletname>/*. Action Specify unique servlet mapping and redeploy the application.
EJPPC0008E: An error occurred when parsing the portlet.xml file. Error: {0}
Explanation An error occurred when parsing the portlet.xml file. Action Check the System log files for the cause of this exception.
EJPPC0009E: An error occurred when parsing the portlet.xml file. Error: {0}
Explanation An error occurred when parsing the portlet.xml file. Action Check the System log files for the cause of this exception.
EJPPC0010W: The parser indicates a warning when parsing the portlet.xml file. Error: {0}
Explanation This is a warning. No user action required. Action Check your portlet.xml file and try to fix the problem.
EJPPC0011I: Validation of the portlet.xml file is completed.
Explanation The portlet.xml file contained within this archive has passed validation successfully. Action No action is required.
EJPPC0101W: Error occurred when loading the portlet deployment descriptor extension file. Default configurations are used.
Explanation An Exception was received when trying to load the file portlet deployment descriptor extension file. Action Analyze the log files for the cause of the error.
EJPPC0102W: Error occurred when reading the configuration data of the web application.
Explanation An Exception was received while reading the configuration data of the web application. The portlet container will not be available for this application. Action Analyze the log files for the cause of the error.
EJPPC0201E: An error occurred during MBean activation for MBeans of type portlet and portletapplication.
Explanation An AdminException exception was created when trying to activate the MBean. Action Analyze the System and ffdc log files for the cause of the error.
EJPPC0202E: An error occurred during MBean deactivation for MBeans of type portlet and portletapplication.
Explanation An AdminException exception was created when trying to deactivate the MBean. Action Analyze the System and ffdc log files for the cause of the error.
EJPPC0203E: An error occurred when sending the start notification for the portlet application.
Explanation An MBeanException exception was created when trying to send a notification. Action Analyze the System and ffdc log files for the cause of the error.
EJPPC0204E: An error occurred during listener registration within the portlet application MBean.
Explanation A MalformedObjectNameException exception was created when registering a listener to the MBean. Action Validate that an MBean of the given name exists and analyze the System and ffdc log files for the cause of the error.
EJPPC0205E: An error occurred during unregistration listener within the portletapplication MBean
Explanation An Exception was created when trying to unregister a listener from the MBean. Action Verify that there was a listener registered to the MBean and that the MBean instance exists. Analyze the System and ffdc log files for the cause of the error.
EJPPC0206E: An error occurred during notification handling within the portlet application MBean.
Explanation An exception was created when the MBean notification handler received a message. Action Analyze the System and ffdc 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}
Explanation For the initialization of PMI measurements for a portlet application, both a StatsGroup instance and a StatsInstance instance need to be registered that identifies this portlet application within the system. Action Verify that the portlet application is installed and see the System and ffdc log files for the original cause of the exception.
EJPPC0221E: There was an exception when trying to remove a StatsInstance for portlet application {0}
Explanation When an application is stopped it is removed from the PMI tree. Action Verify 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 instance for portlet {0}
Explanation 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. Action 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.
Explanation Not all capabilities of the portlet container will be available since not all collaborators have been initialized. Action Check that the plugin.xml has the correct format and the referenced class exists.
EJPPC0231E: There was an exception when trying to create the portlet filter.
Explanation Not all capabilities of the portlet container will be available since not all portlet filters have been initialized. Action 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}.
Explanation The portlet container expects the ExtInformationProviderWrapper to be the latest container service wrapper. No custom PortletContainerInvokerCollaborator must wrap this container service later. Action 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.
Explanation The dynamic content provider allows to dynamically add the correct portlet url to the cached content. Action Analyze the log files for the cause of the error.
EJPPC0242E: Error occurred during lookup in application extension registry.
Explanation Collaborators used in applications will not work. Action Check the jndi settings for the application extension registry.
EJPPC0500E: Body illegal for this tag.
Explanation The tag cannot have a body. Action Modify the tag and remove its body.
EJPPC0501E: Insert and State tags must be nested within the Init tag.
Explanation Insert and State tags must be nested within the Init tag. Action Modify the tag so that it is nested within the Init tag.
EJPPC0502E: Urlparam tag must be nested within the State tag.
Explanation Urlparam tag must be nested within the State tag. Action Modify the tag so that it is nested within the State tag.
EJPPC0503E: Only one Init tag allowed per page.
Explanation Only one Init tag allowed per page. Action Modify the page so that there is only one Init tag.
EJPPC0504E: This tag must have a body.
Explanation This tag must have a body. Action Modify the tag so that it contains a body.
EJPPC0505E: Portlet tag must be nested within the Scope tag.
Explanation Urlparam tag must be nested within the Scope tag. Action Modify the tag so that it is nested within the Scope tag.