Page History

java.net.SocketTimeoutException: Read timed out

org.apache.commons.httpclient.ConnectTimeoutException: The host did not accept the connection within timeout of 10000 ms

• The JIRA host connected to the TeamCity host but didn't get any response from it most likely due to network problems.
• Your TeamCity sever might be very slow. Check the CPU load during the indexation.

For possbile issue resolutions, refer to this page.

• The TeamCity user's password in the Application Link is not valid.
• The TeamCity user is authenticated via LDAP. See here for details.

com.stiltsoft.lib.teamcity.connector.rest.exception.HttpStatusNotOkException: HTTP/1.1 502 Proxy Error

or

com.stiltsoft.lib.teamcity.connector.rest.exception.HttpStatusNotOkException: HTTP/1.0 403 Forbidden

JIRA tries to connect to TeamCity via a proxy. For the details on connection via proxy server, refer to this page.

The add-on cannot reach the TeamCity host by the specified URL in the application link. Ensure that you have specified the correct address of the TeamCIty server.

How to verify URL address of TeamCity address:

1. In the browser's address line, enter URL (which you specified in the applicaiton link), then add /httpAuth/app/rest/builds. 
2. Your URL should look like: http://teamcity-server-address/httpAuth/app/rest/builds.
3. Press Enter.
4. Enter login and password.
5. The XML listing with TeamCIty builds should be displayed.

java.net.UnknownHostException

IP address of the specified host cannot be resolved. Ensure that the host specified in the application link is accessible.

1. In the browser's address line, enter the IP address of the host (from the application link).
2. The login form of the TeamCity server should open.

HTTP/1.1 503 Service Unavailable

TeamCity server is temporarily unavailable. This may happen due to high load on the server or due to any other problem.

Try to open TeamCity server in your browser. Address the issue to TeamCity administrator to check the service unavailability.