E
dit
A
ttach
P
rintable
r15 - 2015-05-27 - 16:36:06 - Main.sbagot
You are here:
TWiki
>
Deployment Web
>
DeploymentTroubleshooting
>
IntegrationsTroubleshooting
>
IntegrationsTroubleshootingRTCandBuildforge
>
BuildForgeAndRationalTeamConcertPerformanceTroubleshooting
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!! <img src="" alt="" width="50" height="50" align="right"/> Why does the Rational Team Concert client take a long time to connect to the build agent server? %DKGRAY% Authors: IntegrationsTroubleshootingTeam <br> Build basis: Rational Team Concert 4.x and later %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> When running !BuildLoopTask or "Test Connection" from a Rational Team Concert (RTC) client to connect to the build agents server, the process to get connected to the build server is slow. ---++ Initial assessment ---+++ Symptoms * When you click *Test Connection* under defined build engine in the RTC Eclipse client, it takes 10 seconds or more for the results to come as a pass. ---+++ Impact/scope * This can also contribute to build requests staying in a pending state for longer. ---++ Data gathering and subsequent analysis steps * A third party tool can be used to debug this problem ([[http://www.wireshark.org/][Wireshark]]) * Run Wireshark on the build agent machine and the RTC server machine and capture the interfaces that are being used by both machines. * Run the "Test Connection" from the RTC client. * Now the network communication between the RTC server and the build agent machine will be captured in Wireshark along with other network communication happening on those machines. * Look for the TCP communication that is done from the RTC server machine to the build server machine. * Use Wireshark filter *ip.dst == <rtc.server>* on the capture of the build machine to filter out unnecessary traces * Follow the TCP stream of the RTC server and build machine in Wireshark. * Check all the communication ASCII output. * Look for any other errors reported while checking the source and destination IP address in Wireshark. ---++ Possible causes * Following the TCP stream using Wireshark might show the cause of the delay in some cases. The long delay to pass the connection test might be caused by map drives on the build agent machines that were not resolved. Example: <verbatim> 200 HELLO - BuildForge Agent v7.1.2.2-0-0010 cmd ping username buildadmin password buildadmin go 320 AUTH AuthRunningAs["SYSTEM","NT AUTHORITY",*WinSidUser] 320 AUTH AuthPriv["..........................."] 320 AUTH AuthPriv[".................."] 320 AUTH AuthPriv["......................................."] 320 AUTH AuthPriv[".................."] 320 AUTH AuthPriv["....................."] 320 AUTH AuthPriv["........................"] 320 AUTH AuthPriv["..........................."] 320 AUTH AuthPriv["....................."] 320 AUTH AuthPriv["........................"] 320 AUTH AuthPriv["............"] 320 AUTH AuthPriv[".................."] 320 AUTH AuthPriv["..........................."] 320 AUTH AuthPriv["....................."] 320 AUTH AuthPriv[".................."] 320 AUTH AuthPriv["....................."] 320 AUTH AuthPriv["....................."] 320 AUTH AuthPriv["............"] 320 AUTH AuthPriv["................................."] 320 AUTH AuthPriv[".................."] 320 AUTH AuthPriv[".................."] 320 AUTH AuthPriv[".............................."] 320 AUTH AuthPriv["....................."] 320 AUTH AuthPriv[".............................."] 320 MAP MapError[+53,"\\machine.a\d$","W:"] 320 MAP MapError[+67,"\\machine.b\DD1 (E)","X:"] 320 MAP MapOk["Y:","\\machine.c\d$","Microsoft Windows Network"] 320 MAP MapError[+53,"\\machine.e\d$","Z:"] 320 AUTH AuthOk["buildadmin"] 320 SET EnvSet["BF_AGENT_VERSION","7.1.2.2-0-0010"] 320 SET EnvSet["BF_AGENT_PLATFORM","Windows 2003"] 320 EXEC Locale["Chinese_Taiwan.950"] 320 EXEC Locale["Chinese_Taiwan.950"] 300 HEARTBEAT 1 310 PLAT Windows 2003 320 PING PingOk 251 RESULT 0 260 EOR quit </verbatim> ---++ Possible solutions * You can see that there are !MapErrors reported <verbatim> 320 MAP MapError[+53,"\\machine.a\d$","W:"] 320 MAP MapError[+67,"\\machine.b\DD1 (E)","X:"] 320 MAP MapOk["Y:","\\machine.c\d$","Microsoft Windows Network"] 320 MAP MapError[+53,"\\machine.e\d$","Z:"] </verbatim> * Remove the mapped network drives that are not getting resolved or fix the mapped drives in question so they are accessible. ---+++++!! Related topics: * Still need help troubleshooting your integrations issue? Refer to [[IntegrationsTroubleshooting][Integrations troubleshooting]] for additional topics. ---+++++!! External links: * Wireshark: [[http://www.wireshark.org/][http://www.wireshark.org/]] ---+++++!! Additional contributors: Main.ZeeshanChoudhry <sticky></div></sticky>
E
dit
|
A
ttach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
: r15
<
r14
<
r13
<
r12
<
r11
|
M
ore topic actions
Deployment
Deployment web
Planning and design
Installing and upgrading
Migrating and evolving
Integrating
Administering
Monitoring
Troubleshooting
Community information and contribution guidelines
Create new topic
Topic list
Search
Advanced search
Notify
RSS
Atom
Changes
Statistics
Web preferences
NOTE: Please use the Sandbox web for testing
Status icon key:
To do
Under construction
New
Updated
Constant change
None - stable page
Smaller versions of status icons for inline text:
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use.
Please read the following
disclaimer
.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more
here
.