Why is our reverse proxy server returning an exception when contacting our Jenkins server?
We are experiencing an exception when our reverse proxy server (i.e. IHS server) tries to talk to our Jenkins server using a short name (i.e. jenkins_server) versus a fully qualified name (i.e. jenkins_server.ad.company.com). When analyzing network traffic, WireShark detects that it is unable to find a Hudson header. The first screenshot is a successful handshake using a fully qualified name for our Jenkins server while the second is using a short name. Any ideas on how or where to fix this?
Successful
Failure
Comments
Ralph Schoon
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER Feb 05 '18, 3:54 a.m.This does not seem to be related to the CLM products and maybe very network related. You should consider to ask in other forums for example stack overflow.
Donald Nong
Feb 06 '18, 1:19 a.m.The line that you should focus on is "Exception: java.net.ConnectException: Connection timed out: connect". Also it is not IHS that tries to connect to the Jenkins server, it is the RTC Jenkins plugin that does this.