TeamCity blank page HTTP 500 after fresh install
Hello,
I've got a problem after configuring the TeamCity server. After the initial Setup the page /showAgreement.html is blank and in the log files I get a ClassNotFoundException.
[2018-08-16 16:31:27,598] ERROR - jetbrains.buildServer.SERVER - Error org.apache.jasper.JasperException: java.lang.ClassNotFoundException: org.apache.jsp.changes.changeRows_jsp; while processing request: GET '/runtimeError.html?jsp_precompile=true', from client xx.xx.xx.xx:53633, user-agent "Jakarta Commons-HttpClient/3.1", no auth
org.apache.jasper.JasperException: java.lang.ClassNotFoundException: org.apache.jsp.changes.changeRows_jsp
at org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:176)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:380)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:386)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:330)
at jetbrains.spring.web.TeamCityJSPServletImpl.access$001(TeamCityJSPServletImpl.java:18)
I have tried to restart the server and deleting the work folder as described in the post:
I try to run the TC on a raspian ("Raspbian GNU/Linux 9 (stretch)")
thanks for your Help
Please sign in to leave a comment.
in addition the first error is:
[2018-08-16 16:45:50,719] ERROR - jetbrains.buildServer.SERVER - Error org.apache.jasper.JasperException: Unable to compile class for JSP:
An error occurred at line: [3] in the jsp file: [/WEB-INF/tags/jquery.tag]
org.apache.jsp.tag.web.linkCSS_tag cannot be resolved to a type
null
An error occurred at line: [3] in the jsp file: [/WEB-INF/tags/jquery.tag]
org.apache.jsp.tag.web.linkCSS_tag cannot be resolved to a type
null
An error occurred at line: [10] in the jsp file: [/WEB-INF/tags/jquery.tag]
org.apache.jsp.tag.web.linkScript_tag cannot be resolved to a type
null
An error occurred at line: [10] in the jsp file: [/WEB-INF/tags/jquery.tag]
org.apache.jsp.tag.web.linkScript_tag cannot be resolved to a type
null
An error occurred at line: [19] in the jsp file: [/WEB-INF/tags/jquery.tag]
org.apache.jsp.tag.web.linkScript_tag cannot be resolved to a type
null
An error occurred at line: [19] in the jsp file: [/WEB-INF/tags/jquery.tag]
org.apache.jsp.tag.web.linkScript_tag cannot be resolved to a type
null
Stacktrace:; while processing request: GET '/showAgreement.html', from client 10.1.16.2:37654, no auth
org.apache.jasper.JasperException: Unable to compile class for JSP:
An error occurred at line: [3] in the jsp file: [/WEB-INF/tags/jquery.tag]
org.apache.jsp.tag.web.linkCSS_tag cannot be resolved to a type
null
An error occurred at line: [3] in the jsp file: [/WEB-INF/tags/jquery.tag]
org.apache.jsp.tag.web.linkCSS_tag cannot be resolved to a type
null
An error occurred at line: [10] in the jsp file: [/WEB-INF/tags/jquery.tag]
org.apache.jsp.tag.web.linkScript_tag cannot be resolved to a type
null
An error occurred at line: [10] in the jsp file: [/WEB-INF/tags/jquery.tag]
org.apache.jsp.tag.web.linkScript_tag cannot be resolved to a type
null
An error occurred at line: [19] in the jsp file: [/WEB-INF/tags/jquery.tag]
org.apache.jsp.tag.web.linkScript_tag cannot be resolved to a type
null
An error occurred at line: [19] in the jsp file: [/WEB-INF/tags/jquery.tag]
org.apache.jsp.tag.web.linkScript_tag cannot be resolved to a type
null
Hi Martin,
This error is pretty strange and likely means that the installation got somehow corrupted. We have some options here: https://youtrack.jetbrains.com/issue/TW-38079
A possibility would also be that either some of the jsp files aren't correct, or some of the libraries have been corrupted. Reinstalling should make it work just fine. Should that not be the case, please file an issue in our tracker: https://youtrack.jetbrains.com/issues/TW
Another option, if you were performing an upgrade, is that the old versions of the libraries weren't actually removed, leading to problems similar to what you are experiencing. If it was a fresh install, as you mention, this shouldn't have an impact, but if instead it was an upgrade, it would be worth it checking that there weren't any leftover libraries.
While we haven't explicitly tested the raspberry pi officially and fully, it should work just fine.