Known Issues

Added by Christopher Hamilton, last edited by Kirill Maximov on Dec 26, 2008  (view change)
Search
Searching TeamCity 4.x Documentation
Table of Contents

This page contains a list of workarounds for known issues in TeamCity.

Clearing Browser Cashes

There is a web UI-related issue which some our users have encountered (and it cannot be reproduced on other computers) which is tied with the cached versions of content. If you have come across such problem, make sure your browser does not use cached versions of content by clearing browser caches.

Logging with Log4J in Your Tests

If you use Log4J logging in your tests, in some cases you may miss Log4J output from your logs. In such cases please do the following:

  • Use Log4J 1.2.12
  • For Log4J 1.2.13+, add the "Follow=true" parameter for console appender, used in Log4J configuration: 
    <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
  <param name="Follow" value="true"/>
</appender>

Code Snapshots Highlighting

The code snapshots displayed in the difference viewer as well as duplicates code fragments are highlighted using Colorer native library. For the time being the library does not support 64-bit platforms. However, you can change it by running TeamCity server under 32-bit JVM in 64-bit OS.

NUnit 2.4.6 Performance

Due to an issue in NUnit 2.4.6 (bundled), its performance may be slower than NUnit 2.4.1. For additional information, please refer to the corresponding issue in our issue tracker: TW-4709

StarTeam Performance

Using StarTeam SDK 9.0 instead of StarTeam SDK 9.3 on the TeamCity server can significantly improve VCS performance when there is a slow connection between TeamCity and StarTeam servers.

Agent Service Can Exit on User Logout under Windows x64

The used version of Java Service Wrapper does not fully support Windows 64 and this causes agent launcher process to be killed on user logout. The agent itself will be function until the next restart (server upgrade or agent properties change).

Subversion repositories with NTLM Authorization

If TeamCity has problems connecting to SVN repository, while using NTLM Authentication, add an option to the server JVM options and to the agent options (if you use agent-side checkout):
-Dsvnkit.http.methods=Basic,NTLM
See a related forum post on this issue.

Subversion-related JVM crashes

If JVM crashes while executing SVN-related code (e.g. under org.tmatesoft.svn package), you can try to disable it by either:

  • Passing -Dsvnkit.useJNA=false JVM option to the crashing process (server or agent), or
  • Making NTLM support less prioritative by passing -Dsvnkit.http.methods=Basic,Digest,NTLM JVM option.

Failed Build Can be Reported as a Successful One with Maven 2.0.7

This is a known bug in this version of Maven. Consider using any later version.
In case it's not possible you can patch mvn.bat yourself by replacing the fragment at line 148 of mvn.bat:

:error
set ERROR_CODE=1

with the following one:

:error
if "%OS%"=="Windows_NT" @endlocal
set ERROR_CODE=1

NoClassDefFoundError: junit/framework/TestListener for junit task

This error may occure if you're using custom Ant home (not bundled with TeamCity), and this Ant doesn't contain junit.jar in its lib directory. The workaround to the problem is either to put junit.jar to the ANT_HOME/lib, or to add fork="true" attribute to the junit task. Related issue in our tracker.

Labels