Explanation | The validation of the portlet.xml within this archive has failed. Please check the ffdc log files for more information. |
Action | Please correct the reported problem and analyze the log files for the cause of the exception. |
Explanation | There was an error installing the application due to a missing file. Please check the ffdc log files for more information. |
Action | Please correct the reported problem and analyze the log files for the cause of the exception. |
Explanation | There was an exception when accessing a file on the system. Please check the ffdc log files for more information. |
Action | Please correct the reported problem and analyze the log files for the cause of the exception. |
Explanation | portlet.xml validation caught a ParserConfigurationException. Please check the ffdc log files for more information. |
Action | Please correct the reported problem and analyze the log files for the cause of the exception. |
Explanation | The portlet.xml contained within this archive does not seem to match the schema and needs to be correct. |
Action | Please correct the reported problem and analyze the log files for the cause of the exception. |
Explanation | In order to address portlets via a URL, portlet and servlet names must be different within a WAR file. |
Action | Please correct the reported problem and redeploy the application. |
Explanation | A servletmapping cannot be the same as /<portletname>/* or /portlet/<portletname>/*. |
Action | Please correct the reported problem and redeploy the application. |
Explanation | A fatal error occurred when parsing portlet.xml. |
Action | Please check the log files for the cause of this exception. |
Explanation | An error occurred when parsing portlet.xml. |
Action | Please check the log files for the cause of this exception. |
Explanation | There was a warning. |
Action | Please check your portlet.xml and try to fix the problem. |
Explanation | The portlet.xml contained within this archive has passed validation successfully. |
Action | No action required. |
Explanation | An Exception was received when trying to load the file portlet deployment descriptor extension file. |
Action | Please 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 | Please analyze the log files for the cause of the error. |
Explanation | An AdminException was received when trying to activate the MBean. |
Action | Please analyze the log files for the cause of the error. |
Explanation | An AdminException was received when trying to deactivate the MBean. |
Action | Please analyze the log files for the cause of the error. |
Explanation | An MBeanException was received when trying to send a Notification. |
Action | Please analyze the log files for the cause of the error. |
Explanation | A MalformedObjectNameException was received when trying to register a Listener to the MBean. |
Action | Please validate the name of the MBean is specified correctly and analyze the log files for the cause of the error. |
Explanation | An Exception was received when trying to unregister a Listener from the MBean. |
Action | 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. |
Explanation | An exception was received when the MBean notification handler received a message. |
Action | Please analyze the log files for the cause of the error. |
Explanation | 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. |
Action | Please check that the portlet application is installed and see the log files for the original cause of the excetpion. |
Explanation | When an application is stopped it is removed from the PMI tree. |
Action | Please check 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 | Please 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 | Please 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 | Please 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 | Please analyze the log files for the cause of the error. |
Explanation | Collaborators used in applications will not work. |
Action | Please check the jndi settings for the application extension registry. |