It's all about the answers!

Ask a question

RTC Hudson/Jenkins Exception : No Hudson/Jenkins header found! Test connection FAILED!

Krishnakumar Gurumurthy (877) | asked Jan 29 '15, 6:41 a.m.
 I have setup RTC client 4.0.6 and Jazz Team server 4.0.6. Integrated with Jenkins 1.593 and tested the connection from Jenkins and it works but when I tried to connect Jenkins server from RTC Hudson/Jenkins build engine configuration page, I face 'No Hudson/Jenkins header found!' . I checked the response and found the respective headers. This is impeding my implementation and go live. If anyone has solutions, please provide.

3 answers

permanent link
Krishna Kishore (50112) | answered Jan 29 '15, 9:34 a.m.

Can you try to connect to the jenkins server from the machine where RTC server is running using curl. The curl command is 

curl -k -v -u USER_ID:PASSWORD JENKINS_URL -o out.txt

where JENKINS_URL is as configured in the build engine, and see which response code and headers come back, e.g. normal case is:

< HTTP/1.1 200 OK

< X-Hudson: 1.395

< X-Jenkins: 1.593

Their could be an issue due to SSLV3, check if the curl command works by specifying "sslv3" as a parameter, for example curl -k --sslv3 -v -u USER_ID:PASSWORD JENKINS_URL -o out.txt

if their is an error then the following workaround can be applied

Add the following line to the server.startup batch file (as one other option to JAVA_OPTS) -Dhttps.protocols=TLSv1 and test the connection to jenkins. Server restart is required after adding the option.

permanent link
Krishnakumar Gurumurthy (877) | answered Feb 02 '15, 2:22 a.m.
I am assuming the JVM parameter is to be set on RTC server. We don't have remote access to Jazz team server. Below is the response header for local jenkins server

  1. Status Code: 200 OK
  2. Cache-Control: no-cache,no-store,must-revalidate
  3. Content-Encoding: gzip
  4. Content-Length: 4323
  5. Content-Type: text/html;charset=UTF-8
  6. Expires: 0
  7. Server: Jetty(winstone-2.8)
  8. X-Frame-Options: sameorigin
  9. X-Hudson: 1.395
  10. X-Hudson-CLI-Port: 56154
  11. X-Hudson-Theme: default
  12. X-Instance-Identity: MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA592ah6EA9RTl7lKIkxJv9FnBYhU5JVSyL+Th9mrRUxSJFdXs91irai4/MoIoFioyuKw/qWSYqeXx VFoT8zg6lzEpiYJ3iQuZLN/4eviXn8ck9LvRLe6DBSbJYsKtVBkA39kzvs0zO5ykU13sPE70SbzFQF37okGYnF6X5e1qR8uhNnJq+tu88fSX2NVU8ZkyULcx uBNOh9iA3Y8AL5GPn2R9aOYPlHTBKYA0mHQVCzw9CE5Vb6+318K7wZlE6HNPf86oe2sGUX4v9q8X9d2iDsgw7quiBgebOIhLXrPp6vzrX6bjHEDehApEjiVc cDbD3Y0n+H7I24nmb+/SJxkk1wIDAQAB
  13. X-Jenkins: 1.593
  14. X-Jenkins-CLI-Port: 56154
  15. X-Jenkins-CLI2-Port: 56154
  16. X-Jenkins-Session: 36a7de35
  17. X-SSH-Endpoint: SOLDEV02:56153

We have another Jenkins server where test connection passes. Below is the

response header for the same.

  1. Status Code: 200 OK
  2. Cache-Control: no-cache,no-store,must-revalidate
  3. Content-Encoding: gzip
  4. Content-Length: 6448
  5. Content-Type: text/html;charset=UTF-8
  6. Expires: Thu, 01 Jan 1970 00:00:00 GMT
  7. Server: Jetty(winstone-2.8)
  8. Set-Cookie: JSESSIONID.2713182c=1x97y82abvykrobwz69ft8i21;Path=/;HttpOnly
  9. X-Frame-Options: sameorigin
  10. X-Hudson: 1.395
  11. X-Hudson-CLI-Port: 49233
  12. X-Hudson-Theme: default
  13. X-Instance-Identity: MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEApysM6lB5t1qLMRa+DqB/KqJI3KkuW7cS7AbSd2447+Us0kbQ1o0TnEMEhegbdjfOehjtp2ORcT63 7J0NWdNGm9AXS3fHrDVAPiB52pHJKmR3xBm0sWDbeVFE27UX6mDs6hBMRPA/hML7QGhJdoIQNEcj08CNiDueu8ehfFRX9XYylMTO9t5epD0PiGoAbWrl/Zum RrVGFM8+Pn2icv+tH7aZlNrtKcq2rG7xvpwqfVQlX55z6UKr+gaiD49tCUFfdhlWZzy9RMo+03S2SsHhXZPLK0EF7vnjgAw7+0XSsdMmSq6lTiwKhriCF4s6 9y+aUmRUgybIbFEMgEPFd1q3cwIDAQAB
  14. X-Jenkins: 1.593
  15. X-Jenkins-CLI-Port: 49233
  16. X-Jenkins-CLI2-Port: 49233
  17. X-Jenkins-Session: 225760f0
  18. X-SSH-Endpoint: localhost:49232
I don't see any significant difference between two response headers. Not sure, why my local Jenkins doesn't pass test connection.

permanent link
Krishna Kishore (50112) | answered Feb 02 '15, 3:24 a.m.
From you reply I can understand that their are two very similar Jenkins servers. For the server Jenkins SOLDEV02 (assuming the name from the header values) the connection works and for Jenkins instance running on your local machine the connection fails. The problem could be that the RTC server cannot connect to the server running on your machine. Even though the "Test Connection" is requested on a RTC Eclipse Client, the test is run on the RTC server and if will fail if the RTC server cannot create a connection to the Jenkins server running on your machine. Make sure that the RTC server machine can communicate with local machine and avoid the use of localhost in the Jenkins url.

Your answer

Register or to post your answer.

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.