jetbrains.buildServer.serverSide.buildLog.LogMessageFacade.readSplittedString(LogMessageFacade.java:128)

I am seeing the below exception when trying to access a build log.    How can I debug this?  If I look at the compiler_output table, it has several rows but the message is all null for them.  Other projects work fine.  If I clear the compiler_output table everything works fine.  I am using MSSQL.
Unexpected Error
Error message: none available
Show stacktrace
java.lang.NegativeArraySizeException
   at java.lang.AbstractStringBuilder.<init>(AbstractStringBuilder.java:44)
   at java.lang.StringBuilder.<init>(StringBuilder.java:81)
   at jetbrains.buildServer.serverSide.buildLog.LogMessageFacade.readSplittedString(LogMessageFacade.java:128)
   at jetbrains.buildServer.serverSide.buildLog.LogMessageFacade.readNextMessage(LogMessageFacade.java:37)
   at jetbrains.buildServer.serverSide.buildLog.LogMessageFacade.access$1100(LogMessageFacade.java:124)
   at jetbrains.buildServer.serverSide.buildLog.LogMessageFacade$MessageFinder.getMessage(LogMessageFacade.java:2)
   at jetbrains.buildServer.serverSide.buildLog.LogMessageFacade$4.run(LogMessageFacade.java:17)
   at jetbrains.buildServer.serverSide.buildLog.LogMessageFacade.runExclusively(LogMessageFacade.java:210)
   at jetbrains.buildServer.serverSide.buildLog.LogMessageFacade.getMessage(LogMessageFacade.java:185)
   at jetbrains.buildServer.serverSide.buildLog.BuildLogImpl.getMessage(BuildLogImpl.java:44)
   at jetbrains.buildServer.serverSide.impl.query.SelectCompilerOutputQuery$1.process(SelectCompilerOutputQuery.java:2)
   at jetbrains.buildServer.serverSide.impl.query.SelectCompilerOutputQuery$1.process(SelectCompilerOutputQuery.java:4)
   at jetbrains.buildServer.serverSide.impl.query.GenericQuery.processResultSet(GenericQuery.java:100)
   at jetbrains.buildServer.serverSide.impl.query.GenericQuery.doExecuteQuery(GenericQuery.java:56)
   at jetbrains.buildServer.serverSide.impl.query.GenericQuery.access$100(GenericQuery.java:18)
   at jetbrains.buildServer.serverSide.impl.query.GenericQuery$2.run(GenericQuery.java:1)
   at jetbrains.buildServer.serverSide.impl.DBFacade$4.doInConnection(DBFacade.java:1)
   at jetbrains.buildServer.serverSide.impl.DBFacade$5.doInConnection(DBFacade.java:2)
   at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:341)
   at jetbrains.buildServer.serverSide.impl.DBFacade._runSql(DBFacade.java:81)
   at jetbrains.buildServer.serverSide.impl.DBFacade.runSql(DBFacade.java:56)
   at jetbrains.buildServer.serverSide.impl.query.GenericQuery.execute(GenericQuery.java:73)
   at jetbrains.buildServer.serverSide.impl.query.SelectCompilerOutputQuery.getCompilationErrors(SelectCompilerOutputQuery.java)
   at jetbrains.buildServer.serverSide.stat.BuildStatisticsImpl.<init>(BuildStatisticsImpl.java:59)
   at jetbrains.buildServer.serverSide.stat.BuildStatisticsImpl.<init>(BuildStatisticsImpl.java:65)
   at jetbrains.buildServer.serverSide.stat.BuildStatisticsImpl$3.doInTransaction(BuildStatisticsImpl.java:1)
   at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:128)
   at jetbrains.buildServer.serverSide.stat.BuildStatisticsImpl.createOn(BuildStatisticsImpl.java:3)
   at jetbrains.buildServer.serverSide.impl.BaseBuild.createFullStatistics(BaseBuild.java:27)
   at jetbrains.buildServer.serverSide.impl.FinishedBuildImpl.getFullStatistics(FinishedBuildImpl.java:48)
   at jetbrains.buildServer.controllers.viewLog.ViewLogController.fillModel(ViewLogController.java:19)
   at jetbrains.buildServer.controllers.ProcessingIncomingParameterController.doHandle(ProcessingIncomingParameterController.java:10)
   at jetbrains.buildServer.controllers.BaseController.handleRequestInternal(BaseController.java:60)
   at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
   at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
   at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875)
   at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)
   at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:523)
   at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:453)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
   at jetbrains.spring.web.TeamCityDispatcherServlet.service(TeamCityDispatcherServlet.java:12)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at jetbrains.buildServer.web.ResponseFragmentFilter.doFilter(ResponseFragmentFilter.java:8)
   at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
   at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
   at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
   at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
   at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
   at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
   at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
   at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
   at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
   at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
   at java.lang.Thread.run(Thread.java:595)

3 comments
Comment actions Permalink

How often do you see such exception? Does the problem reproducable?

0
Comment actions Permalink

Until I cleared the compiler_output table it was completely reproducible.  Now that it is cleared, I can no longer reproduce it.    The build had previously failed due to a diskspace issue on the TC server.  I cleaned up the disk and re-ran the build and now everything appears ok.

Since I am evaluating teamcity for purchasing for use in our organization to replace a home-grown build system, anytime I get an error that isn't easy to diagnose is a concern.

0
Comment actions Permalink

Well, my second question would be whether there was incorrect shutdown of the server or disk space issue. In fact such error can only occur if build log is broken. And build log can be broken if server was killed or server was not able to close build log properly. We should detect such situations, but currently it is not true. Please watch/vote for this issue: http://jetbrains.net/tracker/issue/TW-6804

BTW these exceptions are not fatal and will gone when build finishes. The only downside is that build log for this build can be empty.

0

Please sign in to leave a comment.