Explanation | The resource that RRD was attempting to dispatch to was unable to be found (remote side). |
Action | Check to ensure the file exists and is available via a RequestDispatcher include. |
Explanation | RRD caught an IOException when WebSphere was servicing the remote request (remote side). |
Action | Review the logs to determine why the IOException occured while servicing this resource. |
Explanation | RRD caught a ServletException when WebSphere was servicing the remote request (remote side). |
Action | Review the logs to determine why the ServletException occured while servicing this resource. |
Explanation | RRD encountered an exception on the remote side when handling the extension handler chain (remote side). |
Action | Review the logs to determine why the extension handler chain failed to be created. |
Explanation | =RRD encountered an exception on the local side when handling the extension generator chain (local side). |
Action | Review the logs to determine the extension generator chain failed to be created. |
Explanation | RRD caught an IOException when RRD was invoking a handler chain target(remote side). |
Action | Review the logs to determine which handler chain target caused the exception. |
Explanation | RRD caught ServletException when RRD was invoking a handler chain target (remote side). |
Action | Review the error logs to determine which handler chain target caused the exception. |
Explanation | RRD was not able to create the specified extension handler (remote side). |
Action | Review the logs to determine which handler failed to be created. |
Explanation | RRD was not able to initialize the specified extension handler (remote side). |
Action | Review the logs to determine which handler failed to be initialized. |
Explanation | RRD was not able to create the specified extension generator (local side). |
Action | Review the logs to determine which generator failed to be created. |
Explanation | RRD was not able to initialize the specified extension generator (local side). |
Action | Review the logs to determine which generator failed to be initialized. |
Explanation | RRD encountered a SOAPException when trying to locate the remote resource (local side). |
Action | Review the logs to determine why this SOAPException occurred calling this resource. |
Explanation | RRD encountered a RemoteException when trying to locate the remote resource (local side). |
Action | Review the logs to determine why this RemoteException occurred calling this resource. |
Explanation | RRD was unable to create an instance of the specified extension delegator (remote side). |
Action | Ensure that the specified extension delegator class exists and is available on the classpath. |
Explanation | RRD was unable to unwrap the request wrappers to get the internal extension request object. |
Action | Ensure that the specified extension request wrapper wrappered the internal extension request. |
Explanation | RRD was unable to unwrap the response wrappers to get the internal extension response object. |
Action | Ensure that the specified extension response wrapper wrappered the internal extension response. |
Explanation | Servlet specification only permits a PrintWriter or ServletOutputStream to be obtained per response. |
Action | Ensure that only one of these methods is being called for a given response. |
Explanation | Servlet specification only permits a PrintWriter or ServletOutputStream to be obtained per response. |
Action | Ensure that only one of these methods is being called for a given response. |
Explanation | An underlying error occurred while retrieving body extension object data. |
Action | Review the logs to determine why RRD was unable to retrieve the body extension object data. |
Explanation | An underlying error occurred while retrieving header extension object data. |
Action | Review the logs to determine why RRD was unable to retrieve the header extension object data. |
Explanation | An underlying error occurred while setting body extension object data. |
Action | Review the logs to determine why RRD was unable to set the body extension object data. |
Explanation | An underlying error occurred while setting header extension object data. |
Action | Review the logs to determine why RRD was unable to set the header extension object data. |
Explanation | Certain operations cannot be supported in rrd on the remote side such as getInputStream. |
Action | View InfoCenter documentation about limitations of RRD. |
Explanation | RRD encountered a ServletErrorResponse when trying to locate the remote resource (local side). |
Action | Review the logs to determine why this exception occurred attempting to call the remote resource. |
Explanation | Problem was encountering while RRD was adjusting the current web module. |
Action | Review the logs to determine why RRD encountered an exception when attempting to adjust this deployed object. |
Explanation | Problem was encountered when RRD component was starting. |
Action | Review the logs to determine RRD was unable to be started. |
Explanation | RRD failed to register required EMF packages use for remote dispatching. |
Action | Review the logs to determine why the EMF packages were unable to be registered. |
Explanation | Unable to create command to obtain list of managed nodes from runtime. |
Action | Review the logs to determine why RRD was unable to create the command to list managed nodes. |
Explanation | Unable to query runtime to obtain list of managed nodes. |
Action | Review the logs to determine why RRD was unable to execute the command to list managed nodes. |
Explanation | Unable to instantiate delagator class. |
Action | Review the logs to determine why RRD was unable to load the delegation registry item class specified. |
Explanation | Required delegator class was not found matching the criteria for this RRD request. |
Action | Review the logs to determine why a delegator could not be found to handle this request. |
Explanation | The generated URL was not in acceptable URL format. |
Action | Review the logs to determine what URL was generated to see why the failure occured. |
Explanation | EndPointURL was not able to be created when ExtensionGeneratorChain was initialized. |
Action | Review trace for this request to determine why creation of the endpoint URL failed. |
Explanation | IOException occured when attempting to write output generated by remote resource. |
Action | Review trace to see if the network connection between client and server was terminated. |
Explanation | Unable to add handler to register. |
Action | Review the logs to determine why RRD was unable to register the handler with osgi framework. |
Explanation | Unable to add handler to registry. |
Action | Review the logs to determine why the executable extension class for the handler could not be created. |
Explanation | Possible deserialization issue when trying to deserialize extension handler descriptor |
Action | Review the logs to determine why RRD was unable to register the handler with osgi framework. |
Explanation | none. |
Action | Review the logs to determine why RRD was unable to register the handler with osgi framework. |
Explanation | Unable to add generator to register. |
Action | Review the logs to determine why RRD was unable to register the generator with osgi framework. |
Explanation | Unable to add generator to registry. |
Action | Review the logs to determine why RRD was unable to create the executable extension for the generator with osgi framework. |
Explanation | Possible deserialization issue when trying to deserialize extension generator descriptor |
Action | Review the logs to determine why deserialization failed for this extension generator descriptor. |
Explanation | none |
Action | Review the logs to determine why registering this generator with the osgi framework failed. |
Explanation | InitialContext was unable to be instantiated. |
Action | Review the logs to determine why an initial context was not obtained. |
Explanation | Resource was unable to be located by initial context. |
Action | Review the logs to determine why an initial context was not located via lookup. |
Explanation | Order of registry items was unable to be resolved. |
Action | Review extension handler and generator config. |
Explanation | Servlet Exception occured while processing remote request. |
Action | Review the logs to determine why the controller servlet failed to execute the request. |
Explanation | IO Exception occured while processing remote request. |
Action | Review the logs to determine why the controller servlet failed to execute the equest. |
Explanation | Unexpected Exception occured while processing remote request. |
Action | Review the logs to determine why the controller servlet failed to execute the request. |
Explanation | Template factories used for configuring dynacache could not be enabled. |
Action | Review the logs to determine why the esi template factories could not create a dynacache entry. |
Explanation | Directive factories used for configuring dynacache could not be enabled. |
Action | Review the logs to determine why the esi directive factories could not create a dynacache entry. |
Explanation | A cache key was generated that collided with a previous entry. |
Action | Review the logs to determine why the cache key collided with a previous entry. |
Explanation | A cache id template could not be retrieved based on the current cache rules. |
Action | Review the logs to determine why the cache id could not be cached. |
Explanation | The header specifying remote cache rules could not be parsed. |
Action | Review the logs to determine why the surrogate control header could not be parsed. |
Explanation | An invalid directive was specified so nothing can be cached. |
Action | Review the logs to determine why a cache id template could not be created from the directive. |
Explanation | A problem occuring trying to print the response data. |
Action | Review the logs to determine why a response writer could not be obtained to print cached output. |
Explanation | An exception occured intializing the remote cache invalidation context. |
Action | Review the logs to determine why the esi context could not be initialized. |
Explanation | An exception occured getting the security service. |
Action | Review the logs to determine why RRD was unable to obtain the security service. |
Explanation | Unable to reference security properties from default outbound SSL alias. Defaults will be used. |
Action | Review the logs to determine why the default properties file failed to load. |
Explanation | The connection to the invalidation servlet failed. |
Action | Review the logs to determine why the processed body failed to be initialized. |
Explanation | Body from the invalidation servlet could not be processed correctly. |
Action | Review the logs to determine why the processed body failed to be processed. |
Explanation | A invalidation failed for the specified dependency. |
Action | Review the logs to determine why the invalidation failed. |
Explanation | An event indicating a cluster chang was not able to be processed. |
Action | Review the logs to determine why the cluster event could not be processed. |
Explanation | The esi validator listener could not be started. |
Action | Review the logs to determine why the esi validator listener could not be started. |
Explanation | The esi validator listener could not be created. |
Action | Review the logs to determine why the esi validator listener could not be created. |
Explanation | The thread that processes topology change events was unable to process an event. |
Action | Review the logs to determine why the invalidator thread could not process work. |
Explanation | Connection to the invalidator servlet could not be closed |
Action | Review the logs to determine why an exception occured during closing of the virtual connection. |
Explanation | XML data could not be deserialized. |
Action | Review the logs to determine why the data could not be deserialized. |
Explanation | Object could not be serialized. |
Action | Review the logs to determine why the data could not be serialized. |
Explanation | An RRD message block that cannot be understood by this version of RRD was encountered. |
Action | Ensure that compatible versions of RRD are being used. |
Explanation | RRD was unable to determine the corresponding HTTP or HTTPS channel listening port associated with the incoming request port. |
Action | Ensure that there is a corresponding port of this type in the serverindex.xml for this application. |