What it means
An XPages or Java web request failed on the server and the browser was sent an HTTP 500 error. The line names the page that failed, not the cause.
Common causes
- An unhandled SSJS or Java error in the XPage, a custom control or a managed bean
- A missing or unsigned design element, library or plug-in the page depends on
- Access or ECL problems running code as the signer or the current user
- A wider HTTP or JVM problem such as memory pressure or a hung HTTP task
Quick fixes
- Open
error-log-0.xmlandtrace-log-0.xmlinIBM_TECHNICAL_SUPPORT\xpages\logs(or use XPages Log File Reader) to find the real exception - Turn on Display XPage runtime error page in the application's XPages properties while testing
- Check the design was signed by an ID allowed to run unrestricted code, then retest
- If many apps fail at once, collect an NSD and restart HTTP with
restart task http