Explanation | An IOException writing the placeholder for the RequestDispatcher include. |
Action | Verify whether output is correct and identify root cause in logs. |
Explanation | An unexpected error caused ARD request handling to stop. |
Action | Identify root cause in logs. |
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. |
Explanation | Another thread called interrupt on the semaphore. |
Action | Search logs for any indication of the thread that called interrupt. |
Explanation | Some error occured sending the response for a request to the ARD JavaScript. |
Action | Search logs for root cause. |
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. |
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. |
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 you have implemented your own request class implementing IServletRequest, check there first for the origination. |
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. |
Explanation | An internal server error occured trying to retrieve a service |
Action | Search logs for any previous error messages that could have caused this. |
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. |
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. |
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 you have identified that these results were previously retrieved, investigate why the results are being retrieved again. Switching to server side aggregation should help. |
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. |
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. |
Explanation | The number of allowable asynchronous threads has been exceeded. |
Action | Consider increasing the value of maxThreads in resources-pme.xml |
Explanation | An unexpected error occured retrieving the Asynchronous Include work manager. |
Action | Search log files for the indication of the cause of error. |