[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32601) Connection timeout behind a proxy

95 views
Skip to first unread message

sdeschenes@log10solutions.com (JIRA)

unread,
Jan 25, 2016, 4:08:09 PM1/25/16
to jenkinsc...@googlegroups.com
Sylvain Deschenes created an issue
 
Jenkins / Bug JENKINS-32601
Connection timeout behind a proxy
Issue Type: Bug Bug
Assignee: Antonio Mansilla
Components: bitbucket-build-status-notifier-plugin
Created: 25/Jan/16 9:07 PM
Environment: Jenkins v.1.625.3
Runs directly
Is in a private network, access with a proxy.
Priority: Major Major
Reporter: Sylvain Deschenes

I've got this error:

Bitbucket notify on start failed: There was a problem while creating a connection to the remote service.
org.scribe.exceptions.OAuthConnectionException: There was a problem while creating a connection to the remote service.
	at org.scribe.model.Request.send(Request.java:69)
	at org.scribe.model.Request.send(Request.java:75)
	at org.jenkinsci.plugins.bitbucket.api.BitbucketApiService.getAccessToken(BitbucketApiService.java:27)
	at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.notifyBuildStatus(BitbucketBuildStatusNotifier.java:216)
	at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.prebuild(BitbucketBuildStatusNotifier.java:79)
	at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:840)
	at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:835)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:664)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537)
	at hudson.model.Run.execute(Run.java:1741)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:408)
Caused by: java.net.ConnectException: Connection timed out
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:579)
	at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:637)
	at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:160)
	at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
	at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:264)
	at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367)
	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:934)
	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177)
	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1093)
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:250)
	at org.scribe.model.Request.addBody(Request.java:134)
	at org.scribe.model.Request.doSend(Request.java:112)
	at org.scribe.model.Request.send(Request.java:65)
	... 12 more

I've tried a lot of settings without success:

  • Set the environment variable JAVA_TOOL_OPTIONS: -Dhttp.proxyHost=<proxyserver> -Dhttp.proxyPort=8080 -Dhttps.proxyHost=<proxyserver> -Dhttps.proxyPort=8080 in Jenkins configuration with value
  • Set the proxy in the advance tab of plugins configuration.
  • Add to the variable JENKINS_JAVA_OPTIONS: -Dhttp.proxyHost=<proxyserver> -Dhttp.proxyPort=8080 -Dhttps.proxyHost=<proxyserver> -Dhttps.proxyPort=8080 in JENKINS in the file: /etc/sysconfig/jenkins

Nothing is working... Every other plugins and job are working. Only this plugin report an error.

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

antonio.mansilla@flagbit.de (JIRA)

unread,
Feb 3, 2016, 1:40:01 PM2/3/16
to jenkinsc...@googlegroups.com
Antonio Mansilla commented on Bug JENKINS-32601
 
Re: Connection timeout behind a proxy

Hi Sylvain Deschenes, first thank you for reporting the problem, I got it, I'll try to identify the problem asap.

antonio.mansilla@flagbit.de (JIRA)

unread,
Feb 3, 2016, 1:40:01 PM2/3/16
to jenkinsc...@googlegroups.com
Antonio Mansilla started work on Bug JENKINS-32601
 
Change By: Antonio Mansilla
Status: Open In Progress

antonio.mansilla@flagbit.de (JIRA)

unread,
Feb 15, 2017, 8:45:02 AM2/15/17
to jenkinsc...@googlegroups.com
Antonio Mansilla stopped work on Bug JENKINS-32601
 
Change By: Antonio Mansilla
Status: In Progress Open
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

antonio.mansilla@flagbit.de (JIRA)

unread,
Feb 15, 2017, 8:45:02 AM2/15/17
to jenkinsc...@googlegroups.com

I'll close this issue since I'm not be able to reproduce the problem.

antonio.mansilla@flagbit.de (JIRA)

unread,
Feb 15, 2017, 8:45:03 AM2/15/17
to jenkinsc...@googlegroups.com
Antonio Mansilla closed an issue as Cannot Reproduce
 
Change By: Antonio Mansilla
Status: Open Closed
Resolution: Cannot Reproduce
Reply all
Reply to author
Forward
0 new messages