|Title||Connection to TeamTrack hangs for several minutes|
|Assigned user||Gareth Rees|
|Description||When release 0.4.2 attempts to connect to TeamTrack 4407, it hangs for several minutes before connecting.|
|Analysis||The hang occurs in TSServer::ValidateVersion in the TeamShare API, on the line reading "socket->ReceiveString( &errorMsg );". The TeamShare API is waiting for data from the server that doesn't appear.|
TeamShare say that in fact the server isn't sending anything and that this line is deleted in very recent versions of the TeamShare API (see evidence).
|Evidence||I've reproduced this on sandpiper.ravenbrook.com (Windows NT), derekpc.teamshare.com (Windows NT), fork2.perforce.com (Windows 2000) and fork.perforce.com (Windows NT).|
|Created by||Gareth Rees|
|Created on||2001-02-01 21:33:28|
|Last modified by||Francis Irving|
|Last modified on||2002-10-11 16:34:32|
|History||2001-02-01 GDR Created.|
2002-10-11 FAI Changed test reference from "section 3.1" to "section 3" to fit with code reorganisation
|7949||closed||2001-02-01 22:13:23||Gareth Rees||Updated the TeamTrack integration so that it works with (and requires) TeamTrack build 4407. This involved the following changes:
1. Use the new TeamTrack API, as of 2001-01-15.
2. Edited TSServer::ValidateVersion() so that it doesn't hang when connecting. See job000190.
3. Increased the supported_dbver parameter to 27, to match TeamTrack 4407.
4. Updated the Administrator's Guide so that it requires 4407.
|7944||closed||2001-02-01 21:44:20||Gareth Rees||Made the Python interface to TeamTrack work with TeamTrack build 4407.|