Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Before reproducing the problem it makes sense to enable 'DEBUG' log level for TeamCity classes. To do it, change the following section in teamcity-(server|agent)-log4j.xml files:

Code Block
xml
xml

<category name="jetbrains.buildServer">
  <priority value="DEBUG"/>
  <appender-ref ref="ROLL"/>
</category>

...

  • determine what process encounters the error (the actual building process, TeamCity server, or TeamCity agent)
  • try to increase the memory for the process via -Xmx JVM option, like -Xmx512m. The option needs to be passed to the process with problems:
    • if it is the building process itself, use "JVM Command Line Parameters" settings in the build runner. e.g. Inspections builds may specifically need to increase the parameter;
    • if it is TeamCity server, modify runAll.* script or (if server is run as Windows service), use TeamCity/bin/tomcat5w.exe //ES//TeamCity (see more);
    • if it is TeamCity build agent, modify agent.* script
  • if increasing memory does not help, please get the memory dump and send it to us for further analysis:
    • to get a memory dump (hprof file) when OOM error occurs, please add the following JVM option (works for JDK 1.5.0_07+): -XX:+HeapDumpOnOutOfMemoryError;
    • when OOM error occurs next time, java_xxx.hprof file will be created in the process startup directory (TeamCity/bin or buildAgent/bin);
    • please archive and upload this file to ftpvia https://ftpuploads.intellij.net/.uploadsjetbrains.com;
    • let us know about the problem via creating an issue in Jira. Don't forget to provide name of file and version of TeamCity.

...

To turn on debug logging of SVNkit library, uncomment the following lines in the
<TeamCity_server_or_agent_home>\conf\teamcity-(server|agent)-log4j.xml file:

Code Block
xml
xml

<category name="javasvn.output">
  <priority value="DEBUG"/>
  <appender-ref ref="SVN.LOG"/>
</category>

...