[JIRA] [teamconcert-plugin] (JENKINS-29130) RTC Polling broken when Proxy enabled

2015-08-21 Thread djo...@paychex.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Jozis commented on  JENKINS-29130 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: RTC Polling broken when Proxy enabled  
 
 
 
 
 
 
 
 
 
 
http.proxyHost and http.proxyPort are working fine. http.nonProxyHosts is not respected. Can you verify that when you're hitting a host that matches a nonProxyHosts pattern, that it is hitting the target directly? In our environment, the proxy will is not able to forward requests to the host we have added to nonProxyHosts. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [teamconcert-plugin] (JENKINS-29130) RTC Polling broken when Proxy enabled

2015-08-21 Thread anilbha...@in.ibm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anil Bhatia commented on  JENKINS-29130 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: RTC Polling broken when Proxy enabled  
 
 
 
 
 
 
 
 
 
 
Hi, 
Can you please share some details on how you are passing authentication details (username / password)..? Are you also using Winstone..? 
Thanks Anil 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [teamconcert-plugin] (JENKINS-29130) RTC Polling broken when Proxy enabled

2015-08-21 Thread anilbha...@in.ibm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anil Bhatia commented on  JENKINS-29130 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: RTC Polling broken when Proxy enabled  
 
 
 
 
 
 
 
 
 
 
Hi, 
Please try as outlined in the accepted response here: https://jazz.net/forum/questions/158844/unable-to-connect-to-rtc-from-jenkins 
I tried with the following options, and it seems to work fine. 
-Dhttp.proxyHost=https://myproxy -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=myrtcserver 
Please note the following in above line: -Dhttp.proxyHost=http+s+://myproxy 
Thanks Anil 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [teamconcert-plugin] (JENKINS-29130) RTC Polling broken when Proxy enabled

2015-08-21 Thread anilbha...@in.ibm.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anil Bhatia edited a comment on  JENKINS-29130 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: RTC Polling broken when Proxy enabled  
 
 
 
 
 
 
 
 
 
 Hi,Pleasetryasoutlinedintheacceptedresponsehere:https://jazz.net/forum/questions/158844/unable-to-connect-to-rtc-from-jenkinsItriedwiththefollowingoptions,anditseemstoworkfine.-Dhttp.proxyHost=https://myproxy-Dhttp.proxyPort=80-Dhttp.nonProxyHosts=myrtcserverPleasenotethefollowinginaboveline:-Dhttp.proxyHost= http+*s*+ https ://myproxy (-Dhttp...isgivenvaluehttps://...)   ThanksAnil 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [teamconcert-plugin] (JENKINS-29130) RTC Polling broken when Proxy enabled

2015-08-04 Thread clkkish...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Krishna Kishore assigned an issue to Anil Bhatia 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29130 
 
 
 
  RTC Polling broken when Proxy enabled  
 
 
 
 
 
 
 
 
 

Change By:
 
 Krishna Kishore 
 
 
 

Assignee:
 
 AnilBhatia 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [teamconcert-plugin] (JENKINS-29130) RTC Polling broken when Proxy enabled

2015-08-04 Thread mcipo...@paychex.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Cipollone updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29130 
 
 
 
  RTC Polling broken when Proxy enabled  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew Cipollone 
 
 
 
 
 
 
 
 
 
 Hi,WehaveanissuewithRTCpollingwhenwehavetheproxysetinJenkins.Weneedtosethttpandhttpsproxysettingsonthemasterformanyotherapps.SowedothisintheJenkins.xmlfileonthemaster.ButthisseemstobreakpollingonRTCjobs.Jobscanstillpullfilesoutofsourcecontrolbutpollingdoesnotwork.Whatisthedifferencebetweenthese2operations?Givesthebelowstacktraceinthepollinglog: Thefollowingsettingsaresetinthejenkins.xml:-Dhttp.proxyHost=proxy001-Dhttps.proxyHost=proxy001-Dhttp.proxyPort=80-Dhttps.proxyPort=80-Dhttp.nonProxyHosts=*.ourcompanycomain.comOurthoughtsarethattheIBMRTCJenkinsplug-inmaynotberespectingthenonProxyHostjavasettings.SinceourRTCinstanceisinternaltothenetwork,itshouldnotfeedthetrafficdestinedforRTCthroughtheproxy. Anyideas,thisoneiskillingus!:)Anyhelpwouldbegreatlyappreciated!!FATAL:RTC:checkingforchangesfailure:CRJAZ0099EAnHTTPerroroccurredwhenthisURLwasbeingaccessed:https://rtcserver.company.com:9443/ccm2/versionCompatibility?clientVersion=5.0.Errordetails:Remotehostclosedconnectionduringhandshake.com.ibm.team.repository.common.transport.TeamServiceException:CRJAZ0099EAnHTTPerroroccurredwhenthisURLwasbeingaccessed:https://rtcserver.company.com:9443/ccm2/versionCompatibility? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

[JIRA] [teamconcert-plugin] (JENKINS-29130) RTC Polling broken when Proxy enabled

2015-08-04 Thread mcipo...@paychex.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Cipollone updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29130 
 
 
 
  RTC Polling broken when Proxy enabled  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew Cipollone 
 
 
 
 
 
 
 
 
 
 Hi,WehaveanissuewithRTCpollingwhenwehavetheproxysetinJenkins.Weneedtosethttpandhttpsproxysettingsonthemasterformanyotherapps.SowedothisintheJenkins.xmlfileonthemaster.ButthisseemstobreakpollingonRTCjobs.Jobscanstillpullfilesoutofsourcecontrolbutpollingdoesnotwork.Whatisthedifferencebetweenthese2operations?Givesthebelowstacktraceinthepollinglog:Thefollowingsettingsaresetinthejenkins.xml:-Dhttp.proxyHost=proxy001-Dhttps.proxyHost=proxy001-Dhttp.proxyPort=80-Dhttps.proxyPort=80-Dhttp.nonProxyHosts=*. ourcompanycomain ourcompanydomain .comOurthoughtsarethattheIBMRTCJenkinsplug-inmaynotberespectingthenonProxyHostjavasettings.SinceourRTCinstanceisinternaltothenetwork,itshouldnotfeedthetrafficdestinedforRTCthroughtheproxy.Anyideas,thisoneiskillingus!:)Anyhelpwouldbegreatlyappreciated!!FATAL:RTC:checkingforchangesfailure:CRJAZ0099EAnHTTPerroroccurredwhenthisURLwasbeingaccessed:https://rtcserver.company.com:9443/ccm2/versionCompatibility?clientVersion=5.0.Errordetails:Remotehostclosedconnectionduringhandshake.com.ibm.team.repository.common.transport.TeamServiceException:CRJAZ0099EAnHTTPerroroccurredwhenthisURLwasbeingaccessed:https://rtcserver.company.com:9443/ccm2/versionCompatibility? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an 

[JIRA] [teamconcert-plugin] (JENKINS-29130) RTC Polling broken when Proxy enabled

2015-08-04 Thread mcipo...@paychex.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Cipollone updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29130 
 
 
 
  RTC Polling broken when Proxy enabled  
 
 
 
 
 
 
 
 
 

Change By:
 
 Matthew Cipollone 
 
 
 
 
 
 
 
 
 
 Hi,WehaveanissuewithRTCpollingwhenwehavetheproxysetinJenkins.Weneedtosethttpandhttpsproxysettingsonthemasterformanyotherapps.SowedothisintheJenkins.xmlfileonthemaster.ButthisseemstobreakpollingonRTCjobs.Jobscanstillpullfilesoutofsourcecontrolbutpollingdoesnotwork.Whatisthedifferencebetweenthese2operations? Givesthebelowstacktraceinthepollinglog:Thefollowingsettingsaresetinthejenkins.xml:-Dhttp.proxyHost=proxy001-Dhttps.proxyHost=proxy001-Dhttp.proxyPort=80-Dhttps.proxyPort=80-Dhttp.nonProxyHosts=*.ourcompanydomain.comOurthoughtsarethattheIBMRTCJenkinsplug-inmaynotberespectingthe nonProxyHost nonProxyHosts javasettings.SinceourRTCinstanceisinternaltothenetwork,itshouldnotfeedthetrafficdestinedforRTCthroughtheproxy.Anyideas,thisoneiskillingus!:)Anyhelpwouldbegreatlyappreciated!! Givesthebelowstacktraceinthepollinglog: FATAL:RTC:checkingforchangesfailure:CRJAZ0099EAnHTTPerroroccurredwhenthisURLwasbeingaccessed:https://rtcserver.company.com:9443/ccm2/versionCompatibility?clientVersion=5.0.Errordetails:Remotehostclosedconnectionduringhandshake.com.ibm.team.repository.common.transport.TeamServiceException:CRJAZ0099EAnHTTPerroroccurredwhenthisURLwasbeingaccessed:https://rtcserver.company.com:9443/ccm2/versionCompatibility? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and 

[JIRA] [teamconcert-plugin] (JENKINS-29130) RTC Polling broken when Proxy enabled

2015-06-29 Thread bb...@paychex.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 bbonn created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29130 
 
 
 
  RTC Polling broken when Proxy enabled  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 teamconcert-plugin 
 
 
 

Created:
 

 29/Jun/15 3:44 PM 
 
 
 

Environment:
 

 windows 2008 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 bbonn 
 
 
 
 
 
 
 
 
 
 
Hi, 
We have an issue with RTC polling when we have the proxy set in Jenkins. We need to set http and https proxy settings on the master for many other apps. So we do this in the Jenkins.xml file on the master. But this seems to break polling on RTC jobs. Jobs can still pull files out of source control but polling does not work. What is the difference between these 2 operations? Gives the below stack trace in the polling log: 
Any ideas, this one is killing us !  Any help would be greatly appreciated!! 
FATAL: RTC : checking for changes failure: CRJAZ0099E An HTTP error occurred when this URL was being accessed: https://rtcserver.paychex.com:9443/ccm2/versionCompatibility?clientVersion=5.0. Error details: Remote host closed connection during handshake. com.ibm.team.repository.common.transport.TeamServiceException: CRJAZ0099E An HTTP error occurred when this URL was being accessed: https://rtcserver.paychex.com:9443/ccm2/versionCompatibility? 
   

[JIRA] [teamconcert-plugin] (JENKINS-29130) RTC Polling broken when Proxy enabled

2015-06-29 Thread bb...@paychex.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 bbonn updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29130 
 
 
 
  RTC Polling broken when Proxy enabled  
 
 
 
 
 
 
 
 
 

Change By:
 
 bbonn 
 
 
 
 
 
 
 
 
 
 Hi,WehaveanissuewithRTCpollingwhenwehavetheproxysetinJenkins.Weneedtosethttpandhttpsproxysettingsonthemasterformanyotherapps.SowedothisintheJenkins.xmlfileonthemaster.ButthisseemstobreakpollingonRTCjobs.Jobscanstillpullfilesoutofsourcecontrolbutpollingdoesnotwork.Whatisthedifferencebetweenthese2operations?Givesthebelowstacktraceinthepollinglog:Anyideas,thisoneiskillingus!:)Anyhelpwouldbegreatlyappreciated!!FATAL:RTC:checkingforchangesfailure:CRJAZ0099EAnHTTPerroroccurredwhenthisURLwasbeingaccessed:https://rtcserver. paychex company .com:9443/ccm2/versionCompatibility?clientVersion=5.0.Errordetails:Remotehostclosedconnectionduringhandshake.com.ibm.team.repository.common.transport.TeamServiceException:CRJAZ0099EAnHTTPerroroccurredwhenthisURLwasbeingaccessed:https://rtcserver. paychex company .com:9443/ccm2/versionCompatibility? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.