Regarding XPages error information

HCL Domino Domino Forum
1

Hello all,

I am working on XPages related examples using Release 8.5.1

Revision 20091002.1006 (Release 8.5.1)

Standard Configuration.

When ever if there is an error in the XPage, opened the same in browser showing

"Error 500

HTTP Web Server: Command Not Handled Exception"

How can i get the detailed error?

I did search in the forum, few of them are suggesting to use application properties–>XPages–>Errors and timeouts–>Display default error page

I did the same and restarted the client/designer…No changes in the error message.

Please clarify me, if this setting only works on SERVER?

Is there any additional things i have to do for getting detailed error message (stack trace).

thanks,

Sreedhar.

2

Subject: RE: Regarding XPages error information

Hi Sreedhar, I’ve used that setting you mentioned & a more detailed error message displays telling me where the page has hiccupped and why (line with code displayed & possible reason for the error). And I usually am only running locally, not on server.

If you’re not getting a useful error message then maybe there’s something up with your ACL settings.

3

Subject: Two areas to check for errors.

  1. In your application set the default error page in the application properties.

This will give you a stack trace on the webpage.

  1. If you are still getting error 500 then you can check the IBM_TECHNICAL_SUPPORT folder for logs that start with xpages.

They will have the stacktrace of exceptions/errors thrown by Xpages.

4

Subject: Didn’t know about item 2. Thanks!..

5

Subject: Certain XPage errors simply give only that much…

  • I’ve complained to Lotus and even put in a PMR on it, for what good it’s done.

  • Usually this is “embedded” JS, like rendered= or some such, or it could be page event SSJS, like beforePageLoad. Start taking out JS until it works, then you’ll know where the error is. Nothing else you can do at this point.

  • I’ve recently discovered that even try…catch blocks will not always prevent issues. The error will be caught but it will introduce wonkiness later on that page, or even on next page to load. Kinda defeats the purpose, seems like.

Hope this helps…