Express (Distributed operating systems), v8.0 > Reference > Messages
CWRDI
CWRDI0001E: Unable to write include placeholder {0}.
Explanation An IOException writing the placeholder for the RequestDispatcher include. Action Verify whether output is correct and identify root cause in logs.
CWRDI0002E: An unexpected error occured in the ARDChannel {0}
Explanation An unexpected error caused ARD request handling to stop. Action Identify root cause in logs.
CWRDI0003W: WARNING: close has been called with out sending a response {0}
Explanation An error in asynchronous request handling caused a close before a response was sent to the client Action Check logs and identify if the error happens consistently.
CWRDI0004E: Thread was interrupted while waiting for request to finish which is needed for the z/OS specific connection paradigm {0}
Explanation Another thread called interrupt on the semaphore. Action Search logs for any indication of the thread that called interrupt.
CWRDI0005E: Exception sending SC_NOT_MODIFIED status {0}
Explanation Some error occured sending the response for a request to the ARD JavaScript. Action Search logs for root cause.
CWRDI0006E: An exception was caught while processing a fragment {0}
Explanation A fragment was interrupted that was waiting for its include to complete. Action Search logs for any indication of the thread that called interrupt.
CWRDI0007W: Failed to initialize PMI ARDModule {0}
Explanation There was an exception upon initializing the performance monitoring module for ARD. Action Turn off PMI for ARD if not needed or check the logs for an indication of the root cause.
CWRDI0008W: Failed to clone the request, passing original object
Explanation An exception was created while cloning the request for the Asynchronous Include. The original request will be passed, but this can be dangerous because of concurrent access from multiple threads. Action Verify where the exception is coming from. If we have implemented your own request class implementing IServletRequest, check there first for the origination.
CWRDI0009E: Unable to process asynchronous include job.
Explanation The work item for the include dispatch was rejected by the AsynchBeans Work Manager. Action In the Work Manager settings, increase maximum threads or allow them to grow.
CWRDI0010E: Unable to retrieve service {0}
Explanation An internal server error occured trying to retrieve a service Action Search logs for any previous error messages that could have caused this.
CWRDI0011E: Exception from include {0} {1}
Explanation An exception from an asynchronous include occured and was not able to go through error page processing. Action Verify whether the exception in question is coming from customer or application server code.
CWRDI0012W: Exception occured setting completed byte buffers {0}
Explanation The results from an asynchronous include could not be retrieved due to an internal server error Action Search the logs for the exception that caused this.
CWRDI0013E: Unable to retrieve results from asynchronous servlet include.
Explanation An unexpected error occured retrieving the results of the include. This could be from requesting include results with id that is not valid or expired results that have been removed. Action If we have identified that these results were previously retrieved, investigate why the results are being retrieved again. Switching to server side aggregation should help.
CWRDI0014E: Timed out waiting for asynchronous servlet include job to finish.
Explanation The asynchronous include did not finish before the execution timeout elapsed. Action Change asynchronous include execution timeout under WebContainer settings or via AsyncRequestDispatcherConfig api.
CWRDI0015E: Asynchronous include work was rejected by the work manager.
Explanation Work was rejected for execution possibly due to context propagation errors or timeout waiting for job to start. Action If the work manager is configured to allow the thread pool to grow, work could be accepted and not started resulting in a work rejected message. This would happen if the timeout to start a job is reached. If it resulted from a context propagation message, evaluate if there are unnecessary features enabled for the work manager.
CWRDI0016W: Unable to run the include asynchronously so it is being executed synchronously.
Explanation The number of allowable asynchronous threads has been exceeded. Action Consider increasing the value of maxThreads in resources-pme.xml
CWRDI0017W: Unable to retrieve work manager to run Asynchronous Includes.
Explanation An unexpected error occured retrieving the Asynchronous Include work manager. Action Search log files for the indication of the cause of error.