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. |
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. |
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. |
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. |
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. |
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. |
Explanation | A servlet mapping cannot be the same as /<portletname>/* or /portlet/<portletname>/*. |
Action | Specify unique servlet mapping and redeploy the application. |
Explanation | An error occurred when parsing the portlet.xml file. |
Action | Check the System log files for the cause of this exception. |
Explanation | An error occurred when parsing the portlet.xml file. |
Action | Check the System log files for the cause of this exception. |
Explanation | This is a warning. No user action required. |
Action | Check your portlet.xml file and try to fix the problem. |
Explanation | The portlet.xml file contained within this archive has passed validation successfully. |
Action | No action is required. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
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. |
Explanation | Collaborators used in applications will not work. |
Action | Check the jndi settings for the application extension registry. |
Explanation | The tag cannot have a body. |
Action | Modify the tag and remove its body. |
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. |
Explanation | Urlparam tag must be nested within the State tag. |
Action | Modify the tag so that it is nested within the State tag. |
Explanation | Only one Init tag allowed per page. |
Action | Modify the page so that there is only one Init tag. |
Explanation | This tag must have a body. |
Action | Modify the tag so that it contains a body. |
Explanation | Urlparam tag must be nested within the Scope tag. |
Action | Modify the tag so that it is nested within the Scope tag. |