I do have Display XPage runtime errors enabled.
I am going to download the log reader now and install it.
From what I have seen on the server console, it is not consistently happening on the same .xsp. Each time it occurs it is a different .xsp so I don't think it is just one bad line of code on a page. I suppose it could be bad code on one of my page layout controls, but they're pretty light on code.
Are there any exception handling best practices I should be using in xPage development?
I use try { } catch { } blocks in larger javascript code blocks, but I have not been using them on small "in-line" javascript statements, is that a problem?
example:
<xp:image id="image1">
<xp:this.url><![CDATA[#{javascript:if(rowIndex==viewScope.get("gbRow")) {
return "/actn019down.gif";
} else {
return "/actn019.gif";
}}]]>
</xp:this.url>
</xp:image>
I use sessionScope and viewScope regularly, is that a bad practice, do those cause errors if my http session times out after 30 mins? Maybe I am trying to use a sessionScope that no longer exists in the session?
I do have a managed-bean in the application, used on just one page. Am I not recycling objects that would cause the Error 500 after time, when the JVM runs out of memory? I haven't seen any memory related messages in the logs or console. But that may explain why the error is not consistent or reproducible?
I'm baffled.
I'll let you know what the log reader turns up.
- Tyler