xPages and JAVA errors reporting ... its a pain, real pain for me

David Marko  15 May 2011 18:14:23
I'm always crying when having an error  in my JAVA code when working with xPages. I can see just one of these too often :
  • Error 500 = crazy, really crazy !!!
  • HTTP JVM: com.ibm.xsp.exception.EvaluationExceptionEx: Error while executing JavaScript action expression = crazy as well ... no error details at all, see my observations here
  • just common JAVA error traceback = its long, very long, but you find details at least ...

Just wetting your appetite .... This is what you can see on server console using Play!Framework (BTW. very nice piece of code, extraordinary web framework for JAVA).
Very nice, short traceback ... you can easily see whats a problem ...

Image:xPages and JAVA errors reporting ... its a pain, real pain for me

And this is what you can see in browser .... very nice as well. I would really appreciate IBM to work more on JAVA error  reporting ... but its probably impossible for JSF  :-(

Image:xPages and JAVA errors reporting ... its a pain, real pain for me
Comments

1Simon O’Doherty  16.05.2011 8:48:44  xPages and JAVA errors reporting ... its a pain, real pain for me

Error 500 is a server side error. So to determine the root cause you should examine the XPages logs in the IBM_TECHNICAL_SUPPORT folder.

2Martin Jinoch  16.05.2011 10:00:42  xPages and JAVA errors reporting ... its a pain, real pain for me

Did you try catching that EvaluationException in your bean and using java.util.logging.Logger to direct the stack trace to logfile?

3David Marko  16.05.2011 10:21:35  xPages and JAVA errors reporting ... its a pain, real pain for me

This EvaluationException is raised by SSJS, which is just one line of managed method call. So I'm just getting error from SSJS not from my JAVA code. Yes I can find the error using print statement techniques ...

Just wonder where I can report such error as I described fully on Xpages forum. Doesnt seem to me, tak xPages IBM developer are reading xPages discussion forum ...

4Martin Jinoch  16.05.2011 10:42:16  xPages and JAVA errors reporting ... its a pain, real pain for me

Ok, what about try/catch that managed bean method call in SSJS? Wouldn't it produce a little more descriptive output?

TOPlist