‘display error message’ in xpages properties is turned on but does not help.
Searching the web, there is no hint for this message when using 8.5.1.
Further info: on our development and test servers with identical domino version ( 8.51 win 64bit )everything works well. we are not aware of any difference in configuration in the directory.
Have you tried rebooting the server? I had an issue at a customer site with 8.5 where no XPages would show, everything was fine on development server. The customer was not regularly rebooting their Domino server. The problem was connected to the JVM, so shutting down and restarting the server reloaded the JVM and cleared the cache.
Since moving to a regular weekly reboot (shut down and restart the whole box, not just a Domino server restart), the problem has not occurred.
thanks for your idea.unfortunately, we are rebooting the whole machines on a weekly schedule and it happened last weekend. but… I truly believe, that there are issues with the jvm but I can’t say which and why.
Subject: You probably have an error in your SSJS somewhere…
8.5.x is utterly useless when it comes to certain, numerous, SSJS errors. This goofy Error 500 is all you get, or a stack trace with an erroneous .xsp file given, and it’s all you will ever get. I’d use print() in your SSJS to attempt to figure out what line it thinks is wrong. You could also do a try…catch and at least prevent it from crashing, with a print() in the catch, and that may point you in the right direction.- Failing that, I’d copy your Xpage/custom control and rip out all JS across the board. Then paste it back it from the copy, one set of JS at a time, until it barfs. Then you’ll at least know what bit of code is causing the problem. When I say paste it back in, I mean use the Source tab to copy and paste the XML, so you know for certain you are using exactly the same code and execution state ($ or #) as the one that breaks.
It’s sort of like debugging Field Formula, only all the code can be seen in the Source tab instead of forcing you to click through a zillion elements individually.
If you’re not using SSJS then I hope your PMR yields results. Bear in mind that SSJS pops up all over in XPages; on buttons, in events, and myriads of other places. Don’t assume any given code is client-side unless there’s a good reason to do so.
I have a PMR in on this very thing … XPage errors are often useless for troubleshooting. Last status two weeks ago was “the next level of support” is checking if they are reproducible and “will create SPRs”.
yes… thanks for your post.I’ve already tried to create a very simple xpage in another database… just label and editbox, definitely without any js logic.
it did not work as well … same http 500 error.
will try prints in beforepageload tomorrow…maybe this will give me a clue.
thank you for the hint, but build automatically is turned on. we also ‘cleaned’ the project multiple times but it does not help as well.btw: in the notes client, everything works fine.
