error 500 http web server: command not handled exception

0
votes

JVM ERRORI think this topic a lot of ppl post it already. I also look for lot of thread in stack overflow and some ibm page. They do give some comment of how to solve this problem. But i still facing the same problem, it still give this error.

Case start : Actually one of my customer, they have facing this error during running on webpages and also notes ~ error 500 http web server: command not handled exception

Action taken but not solve:

  • The user id signing/creating the XPages allowed to run XPages in the server document?
  • Do project clean, build automatically on designer
  • Do testing on creating new xpages page with simple lable " hello world" , this one can run successfully only.
  • Try to reload the http server by

tell http quit
load http

After do this the problem still same give the same error. May i know got any other way to solve it? Error LogError Log2 trace log

3
xpagesxpages-ssjsxpages-extlib
I backup the customer database and run on local does not have any problem on opening it~ - Desmond Sim
That issue can can be almost anything. Without code examples it is impossible to even start making suggestions. Additional information is needed. Have you looked at web log or error logs on the server? - Eric Tomenga
HTTP JVM: CLFAD0211E: Exception thrown. For more detailed information, please consult error-log-0.xml located in D:/Lotus/Domino/data/domino/workspace/logs , do you means this log file? - Desmond Sim
Install XPages Log File Reader from OpenNTF which gives you easy access to the XPages log files. The log file will tell you the reason for the error 500. - Per Henrik Lausten

3 Answers

3
votes

"Unresolved compilation errors: java.lang.String" points to a failed install as here. A class in java.lang or java.util should always be resolved. Ensure all services and any processes for Notes / Domino are stopped before the relevant install, jar files can get locked once used. Xpages can't load, Error 500; java.util cannot be resolved

1
votes

Switch on "Display XPage runtime error page" in application's XSP Properties then you'll see a detailed error message which probably will lead you to the issue:

enter image description here

0
votes

I frequently get this error when there is a mismatch/problem with access rights or the user login has expired and the app/database doesn't redirect to the login page. I suggest you double check the security basics first. (Might also explain why the app works locally, but not on the server).